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

[Philip Nienhuis]

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

This looks like a sort of duplicate, or extension, of patch #9746. As I wrote
there it's not too hard to extend the wmemory.m there to also report various
RAM sizes using Windows' "systeminfo" command:

>> outval = system ("systeminfo");
:
:
Total Physical Memory:     7 887 MB
Available Physical Memory: 5 126 MB
Virtual Memory: Max Size:  15 772 MB
Virtual Memory: Available: 12 719 MB
Virtual Memory: In Use:    3 053 MB
:


(note: echoed to screen, NOT returned in outval)

.. and obviously Windows has built-in binary library functions that give that
info right away, rather than complete with the entire OS hotfix history that
"systeminfo" helpfully echos as well. After all, "systeminfo" gets its info
from /somewhere/.

As outlined in the relevant maintainers ML thread where you first posted
today, at
https://github.com/octave-de/macgyver_utils/blob/master/memory.m
there's a memory.m (GPL AFAICS) which seems to work on MacOSX, Linux and
Windows. In that memory.m my patch turns out to be absorbed.

What do you think, could that file be combined with yours or vice versa, and
the trick I used above be added somehow?
That way we can have one comprehensive function for exploring RAM usage.
Making it Matlab-compatible can be done in a next step by calling it by
Matlab-compatible wrapper functions.


    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/patch/?9924>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/