Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add memory diagnostic Postporcessor #8619

Closed
dschwen opened this issue Feb 23, 2017 · 3 comments
Closed

Add memory diagnostic Postporcessor #8619

dschwen opened this issue Feb 23, 2017 · 3 comments
Labels
C: Framework P: normal A defect affecting operation with a low possibility of significantly affects. T: task An enhancement to the software.

Comments

@dschwen
Copy link
Member

dschwen commented Feb 23, 2017

Description of the enhancement or error report

We have PerformanceData as a Postprocessor, which focusses on execution times. I'd like to have a similar PP to give me data on memory consumption.

Rationale for the enhancement or information for reproducing the error

On HPC runs memory data would be useful. I'd like to see virtual memory used, resident size, and major page faults (i.e. page swapping I/O events from RAM to Disk and vice versa)

Identified impact

Added capability
dschwen added a commit to dschwen/moose that referenced this issue Feb 23, 2017
@dschwen
Add memory usage diagnostic Postprocessor (idaholab#8619)
f6caf92
dschwen added a commit to dschwen/moose that referenced this issue Feb 23, 2017
@dschwen
Add memory usage diagnostic Postprocessor (idaholab#8619)
beb0ff9
dschwen added a commit to dschwen/moose that referenced this issue Feb 23, 2017
@dschwen
Add "test" (idaholab#8619)
49d8180
dschwen added a commit to dschwen/moose that referenced this issue Feb 23, 2017
@dschwen
Add memory usage diagnostic Postprocessor (idaholab#8619)
613dd13
dschwen added a commit to dschwen/moose that referenced this issue Feb 23, 2017
@dschwen
Add "test" (idaholab#8619)
021bca6
@dschwen
Copy link
Member Author

dschwen commented Feb 23, 2017 •
edited

Initial test with increasing mesh refinement at each step. Lines are the new PP, symbols are the memory logger.

image

@dschwen
Copy link
Member Author

dschwen commented Feb 24, 2017

Actual Cahn-Hilliard run on 4 cores:
image

@permcody
Copy link
Member

This is looking promising. Thanks!

@permcody permcody added C: Framework P: normal A defect affecting operation with a low possibility of significantly affects. T: task An enhancement to the software. labels Feb 24, 2017
dschwen added a commit to dschwen/moose that referenced this issue Mar 7, 2017
@dschwen
Add memory usage diagnostic Postprocessor (idaholab#8619)
6572c9f
@dschwen dschwen mentioned this issue Mar 7, 2017
Merged
dschwen added a commit to dschwen/moose that referenced this issue Mar 7, 2017
@dschwen
Add memory usage diagnostic Postprocessor (idaholab#8619)
7780b40
dschwen added a commit to dschwen/moose that referenced this issue Mar 7, 2017
@dschwen
Add documentation (idaholab#8619)
70ac724
dschwen added a commit to dschwen/moose that referenced this issue Mar 10, 2017
@dschwen
Add memory usage diagnostic Postprocessor (idaholab#8619)
6f6a19d
dschwen added a commit to dschwen/moose that referenced this issue Mar 10, 2017
@dschwen
Add documentation (idaholab#8619)
2ab224a
dschwen added a commit to dschwen/moose that referenced this issue Mar 10, 2017
@dschwen
Address comments (idaholab#8619)
d95759b
dschwen added a commit to dschwen/moose that referenced this issue Mar 13, 2017
@dschwen
Address valgrind issue (idaholab#8619)
91be98a
@dschwen dschwen mentioned this issue Mar 13, 2017
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
C: Framework P: normal A defect affecting operation with a low possibility of significantly affects. T: task An enhancement to the software.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@dschwen @permcody