Support Board
Date/Time: Sun, 22 Feb 2026 00:45:56 +0000
Post From: OS Timers vs SC Timers discussion again... SC Timers chart update limitations
| [2026-01-28 18:00:50] |
| User719512 - Posts: 419 |
|
Frederik, you can't write to the log every iteration and expect to measure perf at levels like 20ms; well at least I would not. You could track/accumulate over say 10 seconds and get avg min max or something and log that, reset, and accumulate again. For the most accurate timings on Windows, you'd want to incorporate Performance Counters. Instead of logging, using GDI/Graphics is very low overhead for more real-time visualizations. I get a good steady state after ~5 seconds. And at 20ms settings, my chart/machine will measure ~33ms for a single chart/DOM test chart setup. The study was called 211 times in 7 seconds for about 30 times a second or 33ms interval (see attached). There are parts in play not measured like Sierra's own processing time, OS overhead for network and file I/O etc. Measuring a single study perf for "how often can my study get called" seems close enough to gauge responsiveness so I never expect to "see" 20ms with that setting. During replay, I have seen sub ~10ms updates with the same setup. I don't think my CPU/GPU would get me much past that. I don't think Update Always will go faster than Chart Update Interval, so might check/verify that. Sierra is blazingly fast. |
 Screenshot 2026-01-28 093344.png / V - Attached On 2026-01-28 17:52:15 UTC - Size: 194.95 KB - 31 views Screenshot 2026-01-28 094133.png / V - Attached On 2026-01-28 17:52:20 UTC - Size: 202.74 KB - 30 views |