Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • ParaView ParaView
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1,962
    • Issues 1,962
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 98
    • Merge requests 98
  • 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
  • ParaViewParaView
  • ParaViewParaView
  • Issues
  • #18915
Closed
Open
Issue created Apr 04, 2019 by Mathieu Westphal@mwestphalMaintainer

primusrun is not using discrete GPU with paraview

with a builded ParaView (5.6 or master), on a laptop with a discrete nvidia card and an integrated intel chipset, the following behavior can be observed :

./bin/paraview
Help -> About -> OpenGL : Mesa...

optirun ./bin/paraview
Help -> About -> OpenGL : Nvidia...

primusrun ./bin/paraview
Help -> About -> OpenGL : Mesa 

The last part is unexepected

With ParaView 5.6 release, this behavior does not appear.

This behavior is not only a reporting error but a performance drop with complex rendering can also be observed.

glxinfo and glxgears do not show this behavior.

On ArchLinux, with nvidia 418.56, bumblebee 3.2.1, primus 20151110

Edited Apr 04, 2019 by Mathieu Westphal
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking