|
I've been running into similar performance issues with
the TreeView, using a liststore containing thousands of rows. For example, with about 40K rows with 10 columns the data loads into the store quickly and then the cpu races for around 30-40 seconds. I think what is going on is the treeview is doing calculations to decide how much space and padding each column needs. I had hoped that having fixed widths would mean no calculations needed to be done, but I still get the same cpu racing. If I watch the treeview carefully while this goes on I see a small shift in the layout of data within each column, moving from left to right (presumably as the code loops through the columns). My suspicion is that the treeview is calculating the layout of the renderers within the the fixed width of each column. I'm guessing if there was an option to stop it doing this (since its initial layout is more than good enough for me) that we would see a dramatic speed improvement. When I get time I was intending to take a look at this, but if there is someone out there more familiar with the treeview code -- that means anyone who has actually looked at it :) then a few pointers would be most welcome. John Igor Gorbounov wrote:
|