octave-bug-tracker
[Top][All Lists]
Advanced

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

[Octave-bug-tracker] [bug #62409] [octave forge] (image) BIST errors on


From: Hartmut
Subject: [Octave-bug-tracker] [bug #62409] [octave forge] (image) BIST errors on 32-bit
Date: Sun, 8 May 2022 11:54:07 -0400 (EDT)

Follow-up Comment #4, bug #62409 (project octave):

I am able to reproduce this "out of memory" with Octave w32 under Windows
(with 16 GB of RAM).

Here is the piece of code that eventually fails when running the first test
mentioned in comment #0:


clear
ind = rand(3780000,8);
stride = 592794;
limit = 2370816;
ind_new = bsxfun (@plus, ind(:), (0:stride:limit));


The resulting vector ind_new should have 1.2e8 elements (when running the code
witha 64bit indexing instead). I am not quite sure how much memory bsxfun
internally occupies during this calculation, but it maybe needs more then the
available 2.1e9, which is "only" 20-times more.

@Markus: Does the above memory consumption of bsxfun seem reasonable to you?

@Avinoam: This probably means we need to reduce the matrix size of those BIST
tests, or do you have a better idea?



    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?62409>

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




reply via email to

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