Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • tnl-dev tnl-dev
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 36
    • Issues 36
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 4
    • Merge requests 4
  • Deployments
    • Deployments
    • Releases
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • TNL
  • tnl-devtnl-dev
  • Issues
  • #92

Closed
Open
Created Sep 28, 2021 by Jakub Klinkovský@klinkovskyOwner

Sparse matrices with 64-bit indices for addressing values, but 32-bit storage for column indices

E.g. PE has a matrix 471526400 x 471526400 with 3099301688 non-zeros. A 64-bit type is necessary to address the non-zero values and column indices in the global arrays, but we can store the column indices as 32-bit only. This would save about 25% of space (double + int vs double + long int).

See also https://github.com/pyamg/pyamg/issues/277

Assignee
Assign to
Time tracking