Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • elpa elpa
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 21
    • Issues 21
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 2
    • Merge requests 2
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • elpa
  • elpaelpa
  • Issues
  • #72

Closed
Open
Created Oct 29, 2019 by Pavel Kus@pkus

lift the restriction bandwidth == nblk in the GPU version of ELPA 2

For the GPU version of ELPA 2, the intermediate bandwidth is always taken as the scalapack block size. It would be better, if the optimal value (as for the CPU version) could be selected, since it is very important for performance. It is, however, hard-coded somewhere in the band reduction step.

Assignee
Assign to
Time tracking