[Kst] 2.0.8

Ben Lewis egretengineering at gmail.com
Mon Feb 24 21:52:42 UTC 2014

Thanks Barth,

That makes sense.

Regards, Ben

On 25/02/2014 8:38 AM, Barth Netterfield wrote:
> I see the same thing.  This has nothing to do with the data source.
> The issue is that it takes a while to process and re-draw a 46million point
> vector.
> Re-drawing in this situation will always be ~slow as adding new data means
> recalculating the whole curve: adding new data the end will rescale the curve
> in X, every time.  I might be able to come up with some faster min/max caching
> method which would sacrifice pixel-level accuracy for speed.
> But this won't happen for 2.0.8.
> As a work around: if the data are slowly varying, you might consider doing a
> skip-read to read every 100th point or something like that, which will speed
> things up dramatically.
> cbn
> On February 25, 2014 07:48:54 AM you wrote:
>> Hi Barth,
>> Attached is my log file.
>> It starts off reading about 2,400 samples per update and slows down to
>> 16,500 samples over an eight hour period of logging. Kst is configured to
>> update every 1000 ms.
>> Do you see this behaviour?
>> I did not see an instance where Kst read the entire vector, so I think your
>> temporary fix has solved that problem.
>> Ben

More information about the Kst mailing list