[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: octave memory
From: |
John W. Eaton |
Subject: |
Re: octave memory |
Date: |
Wed, 11 Feb 2009 15:37:12 -0500 |
On 11-Feb-2009, Miroslaw Kwasniak wrote:
| Current kernels have an entry /proc/*/status:
|
| $ grep Vm /proc/`pidof octave-3.0.1`/status
| VmPeak: 419416 kB <- max allocated
| VmSize: 321288 kB
| VmLck: 0 kB
| VmHWM: 106716 kB <- max used (HWM = High Water Mark)
| VmRSS: 105828 kB
| VmData: 253276 kB
| VmStk: 312 kB
| VmExe: 4 kB
| VmLib: 47508 kB
| VmPTE: 288 kB
|
| I assume VmHWM is a true max usage when not swapped.
|
| Below the same process listed by top:
|
| PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
| 18177 mirek 39 19 399m 103m 24m S 1.6 6.8 32:49.40 octave-3.0.1
So why isn't this information returned by the getrusage library
function? I don't think Octave (and every other program that might
want this info) should have its own code for getting this info from
/proc (which doesn't seem portable anyway). I thought that's what the
getrusage library function was for...
jwe
- Re: octave memory, Søren Hauberg, 2009/02/11
- Re: octave memory, John W. Eaton, 2009/02/11
- Re: octave memory, jean francois sauvage, 2009/02/11
- Re: octave memory, Jaroslav Hajek, 2009/02/11
- Re: octave memory, jean francois sauvage, 2009/02/11
- Re: octave memory, John W. Eaton, 2009/02/11
- Re: octave memory, Miroslaw Kwasniak, 2009/02/11
- Re: octave memory,
John W. Eaton <=
- Re: octave memory, Thomas Weber, 2009/02/12
- Re: octave memory, Miroslaw Kwasniak, 2009/02/12
- Re: octave memory, jean francois sauvage, 2009/02/12
Re: octave memory, Rob Mahurin, 2009/02/11