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

[Philip Nienhuis]

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

Turns out I already have (more or less by accident) a 64-bit Octave-3.9.1+
without 64-bit indexing - it seems I simply forgot that I configured MXE with
-enable-windows-64 rather than --enable-64 (which implies
--enable-windows-64). OK I had a week skiing holiday in between and had built
it on my other box, those may be some reasons I forgot it.

Anyway that version can easily accommodate a 30000x30000 double array (7.2 GB)
as well on my Win64 8 GB RAM box.

With an older "pure" 32-bit 3.9.0+ it turns out that rand(8650) (598580000
bytes) is near the max size it can allocate.

The conclusion is that to be able to use RAM > 0.6 GB on 64-bit machines
running 64-bit Windows, an Octave is needed that has been configured & built
with --enable-windows-64 (and runs only on 64-bit Windows).
For "pure" 32-bit Octave builds, the max array size is in the order of 450 to
600 MB.

As to how to further process this bug report, I tend to close it with either:
- "fixed" (as we have --enable-windows-64 build options) or
- "invalid" (as there are Octave options to circumvent the memory limits) or
- "won't fix" (as there's no way out for pure 32-bit builds, like 3.6.4).
What do you think, Dan?


    _______________________________________________________

Reply to this item at:

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

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