[Octave-bug-tracker] [bug #44380] Facing memory limit of less than 1 GB

[Philip Nienhuis]

Follow-up Comment #9, bug #44380 (project octave):

@comment #8: AFAIK Octave doubles occupy 8 bytes.
And yes, for 32-bit programs Windows memory fragmentation an be very bad, see
my comment #2.

@comment #7:
What exactly do you mean with "64-bit Octave 3.8.2" ?
Where did you get your Octave version?

We have three Octave-"bit width" versions on Windows:
- plain 32-bit, runs on 32-bit Windows
- 32-bit indexing but only running on 64-bit Windows
- 64-bit indexing,   ---^^ditto^^---

I think you're running the upper 32-bit version, isn't it? Given your results,
I doubt you have a 64-bit version.


I haven't come around to building the middle type, I only used 64-bit indexing
builds till now, but I'll have time this week to try.

FYI, with Octave-3.9.1+ w. 64-bit indexing and Matlab 2015b prerelease
(64-bit) on 64-bit Win7 8 GB RAM, arrays of 30000x30000 double ("rand
(30000)") could easily be accommodated (as expected, of course) within a mere
10 seconds, total memory occupied by Octave = 7.2 GB, by ML ~7.6 GB. 
I also tried "rand (40000)" but then it took 15 minutes to get it
accommodated, as it overflowed physical RAM capacity and in the end ~5 GB was
in the swap file on hard disk (w. 99 % RAM usage).


    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?44380>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/