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,961
    • Issues 1,961
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 99
    • Merge requests 99
  • 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
  • #3257
Closed
Open
Issue created May 17, 2006 by Kitware Robot@kwrobotOwner

SNL: Spyplot reader problem on node 0

This issue was created automatically from an original Mantis Issue. Further discussion may take place here.


When running paraview on very large AMR CTH data (640 million cells) there is a problem with node 0. We're running 128 node server, and all the nodes are using about 200 meg of memory (including node 0) then at the very end of the read node 0 suddenly goes to like 2 gig of memory and then crashes. I will try to get some large data that replicates this problem... in the meantime someone might look to see what node 0 is 'collecting' at the very end that might be memory intensive when working with 400k datasets (AMR grids) and 460M cells.

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