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,960
    • Issues 1,960
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 95
    • Merge requests 95
  • 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
  • #19385
Closed
Open
Issue created Oct 11, 2019 by Emanuele Leggio@Nanes

StreamTracerWithCustomSource of ParaView 5.7 with SurfaceStreamlines = 1 goes up to 20 times slower than previous versions of ParaView

I conducted many tests with ParaView 5.7 and I noticed that by activating the SurfaceStreamlines in StreamTracerWithCustomSource filter the processing times have increased a lot.
To prove this claim I considered 3 cases with increasing numbers of cells, all surfaces are with triangular mesh, seed point come from the surfaces.

case seed point cell
A 1260 688294
B 11044 5531204
C 92947 40727434

I have tested 4 pre-builded versions of ParaView and two SuperBuild:
Pre-build:

  • 5.3.0
  • 5.4.1
  • 5.5.2
  • 5.7.0

SuperBuild:

  • 5.6.0 (PV5.6SB)
  • 5.7.0 (PV5.7SB)

I tested both the case with SurfaceStreamlines = 1 and SurfaceStreamlines = 0.
Each test was repeated 3 times in order to average the times; only with PV5.7SB I did only one run for each test. A little less than 100 runs in total.
To complete the analysis I report the number of points and cells of the final result in addition to the processing times. Obviously all the tests were conducted on the same machine with the same operating system and in a serial manner without other processes.

RESULTS:

results1

in the attachment you can find the two simple scripts I used to do this analysis and all the intermediate results logs.

execute_streamTraceWCS.py

main_launch.py

results.tar.gz

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