Hi,
First off, I am quite happy with data tree, however if there is really huge amounts of data to be displayed it shows non ideal performance. Do you plan on a caching strategy like for example the datagrid does (that is, render only those controls that are in view)? That would be really cool. At the moment I implemented my own caching by rebuilding the datasource to display only the expanded nodes and allow only one folder and its subfolders to be displayed at the time.
All the best,
Malte
caching strategy planned?
Moderators: FourthWorld, heatherlaine, Klaus, kevinmiller, robinmiller
-
worcestersource
- Posts: 24
- Joined: Wed Mar 17, 2010 3:51 pm
- Contact:
Re: caching strategy planned?
Hi Malte,
Data Tree does use a few tricks to speed it up when handling large amounts of data, so I wonder what might be going on. Even with a thousand nodes, it should display in a flash, although some background cycles may inhibit performance for a second or two afterwards. The new version I'm working on has more things to draw, so if there's anything up I could do with finding out!
In any case, could I ask a few questions?
1. How many nodes are in the data set in total?
2. How many nodes are being drawn at once?
If there's anything else that's special about your tree, please let me know. If you like, you can email me off the forum.
Cheers,
Steve
Data Tree does use a few tricks to speed it up when handling large amounts of data, so I wonder what might be going on. Even with a thousand nodes, it should display in a flash, although some background cycles may inhibit performance for a second or two afterwards. The new version I'm working on has more things to draw, so if there's anything up I could do with finding out!
In any case, could I ask a few questions?
1. How many nodes are in the data set in total?
2. How many nodes are being drawn at once?
If there's anything else that's special about your tree, please let me know. If you like, you can email me off the forum.
Cheers,
Steve