Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • T Trilinos
  • Project information
    • Project information
    • Activity
    • Labels
    • 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
  • #4870

Closed
Open
Created Apr 12, 2019 by James Willenbring@jmwilleOwner

Tpetra::MultiVector::norm*: Prefer running on device

Created by: mhoemmen

@trilinos/tpetra

The Tpetra::MultiVector::norm* methods currently run where the MultiVector's data were most recently updated. Reports from @vbrunini running SPARC with vectors with 1.8 million local rows show that this can cause a slowdown, if running on host. We need to fix these methods so they prefer running on device unless the vector has too few rows to justify running on device.

Assignee
Assign to
Time tracking