[Octave-bug-tracker] [bug #53005] Variable editor: slow performance with large arrays

[John W. Eaton]

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

Yes, we only perform the indexed assignment of the single value.

But then we get the full value back so we update everything on the next
display update.  That part might be easy to fix.  But you also have to
consider the possibility of the variable changing in the interpreter,
independent of the editor.  Currently we don't have a way to mark a variable
(or an element of a variable) as modified and I'm not sure we want the
overhead of doing that just in case it might be open in a GUI variable editor
tab.  So the variables in the editor are refreshed at the prompt.  Maybe we
can do better.  Do you have a concrete suggestion that doesn't impose a
performance penalty even when the variable editor is not used?

Even so, the variable editor should only have to update the elements that are
displayed, not all elements.  That is almost sure to be less than the full
1,000,000 elements for a 1000x1000 array.  More like a few hundred or a
thousand.  But maybe there is a mistake and it is updating all of them for
some reason.  It must currently do that if autofit is enabled.  Do you have
that feature enabled?


    _______________________________________________________

Reply to this item at:

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

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