The Real-Time Graphics Tools for .Net (and Java) products use a different update algorithm than our earlier Windows and DOS products. We no longer update graphs incrementally each time a change is made to the data. The inremental update method always caused problems with other graphical objects in the same plotting area as the scrolling graph objects. Also, we found that if text objects were included in the update, update rates were drastically reduced.
In the .Net product, the data is updated asynchronously with with display. In theory you can update the data 1M updates/second, while only updating the display once a second. We feel that in the long run, this is a superior update technique, because it makes no sense to update the display faster than the eye can follow (20-30 times a second), but actual data update rates can be orders of magnitude faster.
This means though, that until computers get fast enough to maintain an optimal display update rate for a given application, some applicaitons will run much slower than the equivalent incremental update method. This is what you are seeing in the examples you site. That is the tradeoff we made in the software in order for our software to perform optimally on the next generation of computers.
|
Performance considerations.
Posted - 02 May 2006 : 10:34:25
