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

[John W. Eaton]

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

The real performance problem is our QVector<cell> thing.  It's totally
unnecessary, and because we resize it to the full size of the table before
anything has been displayed, we are wasting a lot of memory and time just to
fill it with empty objects that can later be used to hold the table data.

We can just eliminate it entirely and the tableview widget will cache whatever
it needs for display.  When we need other info about a table element, we can
just compute it instead of trying to cache it.  My quick check shows that
performace will be a lot better this way.  And the implementation will be
simpler if we eliminate our cache of "cells".

I can take care of this change after I get some sleep.

I can also see a path to computing formats in the same way as we use for the
terminal display so that decimal points are lined up.  For that, we may want
to limit the application to arrays below a certain size, and if so, make that
limit configurable.

More "tomorrow".

    _______________________________________________________

Reply to this item at:

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

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