Skip to content

GitLab

  • Menu
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,842
    • Issues 1,842
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 89
    • Merge requests 89
  • 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
  • ParaView
  • ParaViewParaView
  • Issues
  • #18762

Closed
Open
Created Feb 10, 2019 by Utkarsh Ayachit@utkarsh.ayachit⛰Owner

too many update information requests

As I am adding logging support to ParaView, simple tasks can cause too many update-pipeline-information requests. While these are often no-ops, they can slow the UI down when in client-server configurations. We should look into it.

Here's the log on simply changing the Clip plane and hitting Apply.

(  27.035s) [paraview        ]   vtkSISourceProxy.cxx:229   INFO| { Clip1: update pipeline(0, 0.000000, true) 
(  27.036s) [paraview        ]   vtkSISourceProxy.cxx:308   INFO| .   { execute vtkPVMetaClipDataSet id: 6663
(  27.037s) [paraview        ]   vtkSISourceProxy.cxx:308   INFO| .   } 0.001 s: execute vtkPVMetaClipDataSet id: 6663
(  27.037s) [paraview        ]   vtkSISourceProxy.cxx:229   INFO| } 0.002 s: Clip1: update pipeline(0, 0.000000, true) 
(  27.043s) [paraview        ]   vtkSISourceProxy.cxx:229   INFO| { Clip1: update pipeline(0, 0.000000, true) 
(  27.044s) [paraview        ]   vtkSISourceProxy.cxx:229   INFO| } 0.000 s: Clip1: update pipeline(0, 0.000000, true) 
(  27.046s) [paraview        ]   vtkSISourceProxy.cxx:229   INFO| { Clip1: update pipeline(0, 0.000000, true) 
(  27.046s) [paraview        ]   vtkSISourceProxy.cxx:229   INFO| } 0.000 s: Clip1: update pipeline(0, 0.000000, true) 
(  27.443s) [paraview        ]   vtkSISourceProxy.cxx:268   INFO| { update pipeline information vtkArrowSource id: 6723
(  27.443s) [paraview        ]   vtkSISourceProxy.cxx:268   INFO| } 0.000 s: update pipeline information vtkArrowSource id: 6723
(  27.444s) [paraview        ]   vtkSISourceProxy.cxx:268   INFO| { update pipeline information vtkConeSource id: 6734
(  27.444s) [paraview        ]   vtkSISourceProxy.cxx:268   INFO| } 0.000 s: update pipeline information vtkConeSource id: 6734
(  27.445s) [paraview        ]   vtkSISourceProxy.cxx:268   INFO| { update pipeline information vtkCubeSource id: 6745
(  27.445s) [paraview        ]   vtkSISourceProxy.cxx:268   INFO| } 0.000 s: update pipeline information vtkCubeSource id: 6745
(  27.446s) [paraview        ]   vtkSISourceProxy.cxx:268   INFO| { update pipeline information vtkCylinderSource id: 6756
(  27.446s) [paraview        ]   vtkSISourceProxy.cxx:268   INFO| } 0.000 s: update pipeline information vtkCylinderSource id: 6756
(  27.447s) [paraview        ]   vtkSISourceProxy.cxx:268   INFO| { update pipeline information vtkLineSource id: 6767
(  27.448s) [paraview        ]   vtkSISourceProxy.cxx:268   INFO| } 0.000 s: update pipeline information vtkLineSource id: 6767
(  27.449s) [paraview        ]   vtkSISourceProxy.cxx:268   INFO| { update pipeline information vtkSphereSource id: 6778
(  27.449s) [paraview        ]   vtkSISourceProxy.cxx:268   INFO| } 0.000 s: update pipeline information vtkSphereSource id: 6778
(  27.450s) [paraview        ]   vtkSISourceProxy.cxx:268   INFO| { update pipeline information vtkGlyphSource2D id: 6789
(  27.450s) [paraview        ]   vtkSISourceProxy.cxx:268   INFO| } 0.000 s: update pipeline information vtkGlyphSource2D id: 6789
(  27.451s) [paraview        ]   vtkSISourceProxy.cxx:268   INFO| { update pipeline information vtkPassThrough id: 6800
(  27.451s) [paraview        ]   vtkSISourceProxy.cxx:268   INFO| } 0.000 s: update pipeline information vtkPassThrough id: 6800
(  27.546s) [paraview        ]   vtkSISourceProxy.cxx:268   INFO| { update pipeline information vtkPVMetaClipDataSet id: 6663
(  27.546s) [paraview        ]   vtkSISourceProxy.cxx:268   INFO| } 0.000 s: update pipeline information vtkPVMetaClipDataSet id: 6663
(  27.547s) [paraview        ]   vtkSISourceProxy.cxx:308   INFO| { execute vtkGeometryRepresentationWithFaces id: 6869
(  27.548s) [paraview        ]   vtkSISourceProxy.cxx:308   INFO| } 0.001 s: execute vtkGeometryRepresentationWithFaces id: 6869
(  27.549s) [paraview        ]   vtkSISourceProxy.cxx:308   INFO| { execute vtkPVExtractSelection id: 6664
(  27.549s) [paraview        ]   vtkSISourceProxy.cxx:308   INFO| } 0.000 s: execute vtkPVExtractSelection id: 6664
( 113.068s) [paraview        ]   vtkSISourceProxy.cxx:268   INFO| { update pipeline information vtkPVMetaClipDataSet id: 6663
( 113.068s) [paraview        ]   vtkSISourceProxy.cxx:268   INFO| } 0.000 s: update pipeline information vtkPVMetaClipDataSet id: 6663
( 113.070s) [paraview        ]   vtkSISourceProxy.cxx:308   INFO| { execute vtkPVMetaClipDataSet id: 6663
( 113.071s) [paraview        ]   vtkSISourceProxy.cxx:308   INFO| } 0.001 s: execute vtkPVMetaClipDataSet id: 6663
( 113.071s) [paraview        ]   vtkSISourceProxy.cxx:308   INFO| { execute vtkGeometryRepresentationWithFaces id: 6869
( 113.074s) [paraview        ]   vtkSISourceProxy.cxx:308   INFO| } 0.002 s: execute vtkGeometryRepresentationWithFaces id: 6869
( 113.075s) [paraview        ]   vtkSISourceProxy.cxx:308   INFO| { execute vtkPVExtractSelection id: 6664
( 113.075s) [paraview        ]   vtkSISourceProxy.cxx:308   INFO| } 0.000 s: execute vtkPVExtractSelection id: 6664

Notice the 3 UpdatePipeline requests on Clip itself and several update information requests.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking