[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-patch-tracker] [patch #9924] Suggestion for a memory() function

From: Lars Kindermann
Subject: [Octave-patch-tracker] [patch #9924] Suggestion for a memory() function
Date: Fri, 1 May 2020 12:27:59 -0400 (EDT)
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Firefox/68.0

Follow-up Comment #12, patch #9924 (project octave):

As I don't have any windows system at hand, I could not add the windows stuff
so far.

About compatibility: I would strongly recommend to keep at least the
"RamAvailableAllArrays" field, maybe renaming it. 

This is basically what I was writing the function for and most people probably
want to know about memory: How much RAM you can use right now. Matlabs
MemAvailable... fields are useless in most cases as putting your data into
swap will slow down anything incredibly.

This value cannot always be derived from other fields in the system struct, as
suggested. The Ram available to a process can be smaller than the free Ram on
the system. This will typically be  the case for 32 Bit systems with more than
4GB of RAM (I implemented this in the RAMAvailabe... field) and when the
process is restricted by the kernel in its memory use, e.g. using cgroups.
(not yet implemented, there is no corresponding field in the /proc/pid/status


Reply to this item at:


  Message sent via Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]