@TricksterX wrote:
Hi!
In the last few days I've been trying to speed up my application. I need to display about 40k nodes, and it's taking about 40 seconds, in which the browser stays completely frozen.
My first attempt was to remove all customization from the node template, which reduced the time by half. Still, 20 seconds is not acceptable, so I tried to use virtualization. In this approach, the initial load is pretty quick, but I lost some features that are essential for the application (expand/collapse hierarchy, change node's parent, localize node).So my doubt is: Is 20~40 seconds the default time for loading this amount of nodes without virtualization? Is it possible to replicate behaviours like expand/collapse and change node's superior with virtualization? If so, is there any examples for that? In the worst case scenario, is it possible to prevent the browser from freezing, so I can display a progress bar animation?
Thanks,
Posts: 6
Participants: 2