Problem with the resources create and solver create time

Hi,
I am interested in the amgx_mpi_possion5pt tutorial.
I compared the solve time and total time with that with a solver in PETSc.

Here is the output from the amgx solver:

mpirun -np 1 ./amgx_mpi_possion5pt.exe -mode dDDI -p 5000 5000 -c PBICGSTAB.json
Invalid MIT-MAGIC-COOKIE-1 keyProcess 0 selecting device 0
AMGX version 2.1.0.131-opensource
Built on Mar 5 2021, 16:22:34
Compiled with CUDA Runtime 10.1, using CUDA driver 11.2
Cannot read file as JSON object, trying as AMGX config
Converting config string to current config version
Parsing configuration string: exception_handling=1 ;
Using Normal MPI (Hostbuffer) communicator...
iter Mem Usage (GB) residual rate
--------------------------------------------------------------
Ini 13.6803 5.000000e+03
0 13.6803 1.863238e+02 0.0373
6 13.6920 5.114025e-07 0.0404
--------------------------------------------------------------
Total Iterations: 7
Avg Convergence Rate: 0.0374
Final Residual: 5.114025e-07
Total Reduction in Residual: 1.022805e-10
Maximum Memory Usage: 13.692 GB
--------------------------------------------------------------
Total Time: 1.74159
setup: 1.28347 s
solve: 0.458115 s
solve(per iteration): 0.0654451 s
resources create 373.340718
create matrix 0.000109
create vectors 0.000013
solver create 104.717192
solver setup 3.145772
solver time 0.458062
solver status 0.000003
Total time 481.661869

Here is the output from the hypre solver in the Petsc with 32 processing elements
nx 5000 ny 5000
setup time 0.066932
fill matrix: time 0.238816
set up vectors:time 0.009836
setup ksp 0.02139
Solve 4.44923
Total 4.78621

The total time to solve the linear system with Amgx solver is very high compared to that with PETSc.
The linear solve time of Amgx solver is less compared to PETSc solver.
In Amgx, why the resources creation and solver creation is outrageously high compared to linear solver setup or solve time. How can I fix it.

Thank you.

Start with the amgx_mpi_possion5pt tutorial and PBICGSTAB.json, reproducing the reported mpirun command and timing output. Trace the resource creation and solver creation stages, then compare them with the solve and PETSc timings; done means identifying the source of the overhead and documenting a supported fix or explanation.