[Octave-bug-tracker] [bug #54005] kron performance affected by octave_quit() calls

[Rik]

Follow-up Comment #8, bug #54005 (project octave):

Human reaction time, at least from what I learned in driver's education, is
about 3/4 of a second or 750 milliseconds.  As long as the outermost loop is
executed say once every 500 milliseconds a human isn't going to really
register the delay.

I tried


A = rand (1e4, 10);
B = rand (1, 1e4);
x = kron (A,B)


There is a slight delay after Ctrl+C but nothing that I couldn't live with. 
If I add another factor of 10 to the size of either A or B I get an
out-of-memory error, so this is close to the maximum case for my machine and
still acceptable.


    _______________________________________________________

Reply to this item at:

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

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