wxGrid and Memory Usage

That does seem high, but not outrageously so given the number of cells. You could probably improve things a lot if you are able to retrieve or generate your data and attributes on the fly as needed from within a your table class. The more you cache or precreate the more memory you are going to use.

The values for the grid are calculated before being put in the grid and after they are
retrieved from a database, that is why they are cached. Do you think it would slow down the
application if I were to put the values in a temporary table/file and then grab
the values from there as needed? I haven't done this with wxGrid yet so I am just worried
about performance issues now.

Thanks
Ryan

ryan wrote:

The values for the grid are calculated before being put in the grid
and after they are retrieved from a database, that is why they are
cached. Do you think it would slow down the application if I were to
put the values in a temporary table/file and then grab the values
from there as needed? I haven't done this with wxGrid yet so I am
just worried about performance issues now.

Probably the only way to find out is to try it.

ยทยทยท

--
Robin Dunn
Software Craftsman
http://wxPython.org Java give you jitters? Relax with wxPython!