This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
Hi There, 1) I have done a test: if I have 20 lines and 500 points in each line, the performance is not so bad.(about 1 or 2 seconds) 2)If I have 500 lines and 20 points in each line, the time to load the curves are significantly increased(at least 20 seconds). How can I improve the loading performance at this condition so that it will have same efficiency as in 1) Thanks Gordon |
|
|
|
|
Hello Gordon For each line created, there will be a series (such as LineSeries), and for each line series there will be a Path object created. The construction of the heavy LineSeries and the Path objects is where the performance is going. This is why rendering 500 lines is slower than 20 lines even though the number points is the same. One option would be to try render multiple "lines" in the same LineSeries. You could include a null point in-between each series of points. The problem with this is multiple "lines" would share the same selection state, so if you need each line to be selectable individually, then this approach won't work. Another option would be to show fewer lines on the graph at once. Surely 500 lines is not that human readable. You could have some controls that the user can change which lines get displayed. Other than that, there isn't a way to improve the performance of constructing 500 LineSeries. If you do leave it the way it is, I'd recommend displaying a loading spinner or progress bar. Jason Fauchelle |
|
|
|
