Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • wslda wslda
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • wtools
  • wsldawslda
  • Wiki
  • Setting up diagonalization engine

Setting up diagonalization engine · Changes

Page history
Update Setting up diagonalization engine authored Feb 17, 2021 by Gabriel Wlazłowski's avatar Gabriel Wlazłowski
Show whitespace changes
Inline Side-by-side
Setting-up-diagonalization-engine.md
View page @ 638c009a
......@@ -43,7 +43,7 @@ or
```
It is recommended to use `PZHEEVR`. This engine takes advantage from the fact that typically we extract only a fraction of eigenstates. However, we find that in some rare cases (system dependent) this routine does not work correctly. In such a case, `PZHEEVD` should be used.
# Benchmarks
# Benchmarks & Scalings
| matrix size | p | q | mb | nb | prec. | routine | system | time [sec] | cost |
| ------------|---|---|----|----|--------|---------|--------|------------|------|
| **65,536 = 2x32^3** | 24 | 28 | 8 | 8 | complex| ELPA (1-GPU) | Summit | **118** | **0.52 nh** |
......@@ -63,3 +63,7 @@ It is recommended to use `PZHEEVR`. This engine takes advantage from the fact th
(1-GPU): `ELPA_SOLVER_1STAGE`, `ELPA_2STAGE_COMPLEX_GPU` or `ELPA_2STAGE_REAL_GPU`
(2-GPU): `ELPA_SOLVER_2STAGE`, `ELPA_2STAGE_COMPLEX_GPU` or `ELPA_2STAGE_REAL_GPU`
(2-CPU): `ELPA_SOLVER_2STAGE`, `ELPA_2STAGE_COMPLEX_DEFAULT` or `ELPA_2STAGE_REAL_DEFAULT`
## Plots
These scalings are derived empirically.
![summit-scaling](uploads/902dbf6ba1829c28d250bc105ffc35cf/summit-scaling.png)
\ No newline at end of file
Clone repository
  • API version
  • Automatic interpolations
  • Auxiliary tools
  • Browsing the code
  • Broyden algorithm
  • C and CUDA
  • Campaign of calculations
  • Checking correctness of settings
  • Chemical potentials control
  • Code & Results quality
  • Common failures of static codes
  • Common failures of time dependent codes
  • Computation domain
  • Configuring GPU machine
  • Constraining densities and potentials
View All Pages