You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
No, not even close.
For test 100x100x10 for 5 time steps on topology (1,1,1):
bin/time: Maximum resident set size (kbytes): 73908
proc/status: VmPeak: 465160 kB
amps: Maximum memory used on processor 0 : 102 MB
Those are all very different values.
for a test 100x100x10-5 (4,1,1):
bin/time is useless, only gives one process: Maximum resident set size (kbytes): 56848
amps:
Maximum memory used on processor 0 : 34 MB
Maximum memory used on processor 1 : 35 MB
Maximum memory used on processor 2 : 35 MB
Maximum memory used on processor 3 : 34 MB
total 138 (138000 KB)
I dont think this is a KiB vs KB thing, since any conversion from one to the other does not result in anywhere near the same storage values as the other systems.
Activity
ian-bertolacci commentedon Apr 16, 2020
No, not even close.
For test 100x100x10 for 5 time steps on topology (1,1,1):
bin/time: Maximum resident set size (kbytes): 73908
proc/status: VmPeak: 465160 kB
amps: Maximum memory used on processor 0 : 102 MB
Those are all very different values.
for a test 100x100x10-5 (4,1,1):
bin/time is useless, only gives one process: Maximum resident set size (kbytes): 56848
amps:
Maximum memory used on processor 0 : 34 MB
Maximum memory used on processor 1 : 35 MB
Maximum memory used on processor 2 : 35 MB
Maximum memory used on processor 3 : 34 MB
total 138 (138000 KB)
proc/status
VmPeak: 538340 kB
VmPeak: 538844 kB
VmPeak: 538608 kB
VmPeak: 538404 kB
2154196 KB
I dont think this is a KiB vs KB thing, since any conversion from one to the other does not result in anywhere near the same storage values as the other systems.