bugno

On several clusters, I got some error messages (Caught amgx exception: Cannot allocate pinned memory) + hangs on AmgX when I used static AmgX library instead of shared lib one...

> @pledac does it happen only with static library? Yes, once I switched to libamgxsh.so, the two issues (on two different clusters) vanished. I should add that the hangs on...

Hello, Just to note: to check the ability of AmgX to solve systems with more than 2B rows, I ran the amgx_mpi_poisson7 test. It runs with (2 048 000 000...

Oups, it works with: ``` srun -n 80 amgx_mpi_poisson7 -mode dDDI -p 300 400 400 5 4 4 -c config Number of Levels: 6 LVL ROWS NNZ PARTS SPRSTY Mem...

Ok, thanks marsaev for your answer. I understand that one of the limitation is memory capacity of each device (which probably caused the crash for the 400x400x400=64e6 cells mesh). I...

> In this API we have the "updateA" call which replaces the matrix coefficients and then performs a lighter weight resetup (rather than the full setup). Oh yes, I read...

I ran poisson test case on v100 card with on a bigger test case with no gain on re-setup unhappily. ./poisson -caseName log -mode **AmgX_CSR** -cfgFileName ./AmgX_SolverOptions_Classical.info -Nx 100 -Ny...

Thanks Paul, I will have a look monday.

For Op_Conv_VEF_Face kernel, we notice between 18% and 34% speedup (Nvidia A6000) according our GPU test cases. On H100, the speedup drops between 6% and 14%. And strangely, it seems...

I add Adrien and Rémi to discuss about the benefice/complexity ratio introduced by using scratch memory. To give an idea 30% speedup is the probable gain by using the good...