Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • T Trilinos
  • Project information
    • Project information
    • Activity
    • Labels
    • Planning hierarchy
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 936
    • Issues 936
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 22
    • Merge requests 22
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • James Willenbring
  • Trilinos
  • Issues
  • #4626

Closed
Open
Created Mar 15, 2019 by James Willenbring@jmwilleMaintainer

Belos::MultiVecTraits: Tpetra specialization is slow on GPU, because it creates local MV & thus does extra CUDA allocations

Created by: mhoemmen

@trilinos/belos @trilinos/tpetra @cgcgcg

The Tpetra specialization of Belos::MultiVecTraits has two methods that need to create temporary "local" MultiVector instances. This creation does a new DualView allocation each time. This makes running on the GPU slow, especially for classical Gram-Schmidt in GMRES, or in general whenever doing X^T * Y or X^H * Y for either X or Y having multiple columns.

I am working on a fix. The idea is to maintain a static DualView "pool" that the local MultiVector can view. One must be careful not to let any DualView instance persist past Kokkos::finalize.

Assignee
Assign to
Time tracking