Performance hit when loading nodes in a tree

[vxviper]

Hi, I just wanted to give people working with the tree panel component the heads up.

In ExtJS 3.x nodes were not records, in ExtJS 4.x they are and you would think that the correct way to alter it's properties is through the set function.

Now, suppose you are loading a couple of hundred nodes, and for each node you modify through the set function some of it's attributes (for example, after the store fires the load event). While in 3.x this was not an issue, in 4.x, calling the set function so many times would cause a big performance hit, proportional to the number of nodes and attributes being modified.

Instead, what can be done, is alter the node.data object and, when all the nodes are ready, call the refresh function in the tree view object.

[mitchellsimoens]

Have you tried suspendEvents and resumeEvents?

[vxviper]

Yes, and executed like this:

node.suspendEvents();

node.set('field1', 'value1');
........
node.set('fieldN', 'valueN');

node.resumeEvents();

Still slow compare to the other approach.

[mitchellsimoens]

Try not queuing the events, may have to force the update after the resume

[vxviper]

The events are not queued by default (I passed false to be sure anyway). Still slow.

It looks like the set function has a lot of overhead.