Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Support
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
ParaView
ParaView
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
    • Cycle Analytics
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
  • Issues 2,003
    • Issues 2,003
    • List
    • Boards
    • Labels
    • Milestones
  • Merge Requests 58
    • Merge Requests 58
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Charts
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • ParaView
  • ParaViewParaView
  • Issues
  • #19460

Closed
Open
Opened Nov 12, 2019 by Utkarsh Ayachit@utkarsh.ayachit
  • Report abuse
  • New issue
Report abuse New issue

static builds of paraview search for plugin shared libs on startup

For a static build of ParaView, run as follows:

> env PARAVIEW_LOG_PLUGIN_VERBOSITY=INFO ./bin/pvpython -dr

You'll see output as follows:

...
(   0.334s) [paraview        ] vtkPVPluginTracker.cxx:405   INFO| Trying to locate plugin with name `VTKmFilters`
(   0.334s) [paraview        ] vtkPVPluginTracker.cxx:105   INFO| { looking for plugin 'VTKmFilters'
(   0.334s) [paraview        ]vtkResourceFileLocator.:61    INFO| .   { looking for 'VTKmFilters.so'
...

This implies that ParaView is wasting time attempting to find files for plugins to load which are never present or loadable in static builds. This should be fixed to improve HPC performance.

Assignee
Assign to
5.8 (Winter 2020)
Milestone
5.8 (Winter 2020)
Assign milestone
Time tracking
None
Due date
None
3
Labels
priority:required project:sandia project:watney
Assign labels
  • View project labels
Reference: paraview/paraview#19460