Is it reasonable that time cost of diagonalization by scalapack_gvx is 7 times longer than that by genelpa #2295
Unanswered
pxlxingliang
asked this question in
Q&A
Replies: 2 comments
-
Comparing with this commit Perhaps the same reason for this issue? |
Beta Was this translation helpful? Give feedback.
0 replies
-
It seems not a same issue. In this issue the slower is compared to genelpa, and is found in version V3.1.0 (may also exist in earlier versions). |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Describe the bug
For the below example, the total time of the LCAO SCF calculation by scalapack_gvx is about 3 times longer than that by genelpa, and the longer of diagonalization (hamiltSolvePsiK) is 7 times.
The detail of the time cost is:

The left one is for scalapack_gvx and the right one is for genelpa.
006_Ti15.zip
Expected behavior
No response
To Reproduce
set
ks_solver
to bescalapack_gvx
andgenelpa
respectively, and run the job with commandOMP_NUM_THREADS=1 mpirun -np 16 abacus
Environment
Bohrium image: registry.dp.tech/dptech/abacus:3.1.0
Additional Context
No response
Beta Was this translation helpful? Give feedback.
All reactions