Support Board
Date/Time: Sat, 23 Nov 2024 05:25:28 +0000
Post From: 2675 Unusable - Freezes
| [2024-09-12 18:03:41] |
| n8trading - Posts: 36 |
|
Ok, I read all of the details about the latest timer message code changes in your posts from #99 to #101 in your "What is Sierra Chart Working On" thread. I'd love to understand more detail as to why you might want to have another timer message code option in addition to or instead of WM_TIMER. From what I gather, using WM_TIMER is causing Sierra Chart to update charts more quickly even though the chart update interval setting hasn't changed. This in itself isn't a bug or issue, but this is what is causing confusion when users update and see that SC UI is less responsive and/or has higher CPU usage after updating to the version that uses WM_TIMER. For me personally, because of the 500ms interval limit, I cannot achieve the same or less CPU usage in the latest version that uses WM_TIMER because setting the interval to 500ms is still causing SC to update faster than before the WM_TIMER implementation and having a lower chart update interval setting. So as I mentioned in my previous post, increasing the update interval limit might be an option, or as you said, maybe giving an option to use a different message code would suffice; And if I understand correctly, would allow the update interval setting to be accurate and SC would update to exactly what value is set. It seems that WM_TIMER works well though, so maybe just re-working the update interval settings to coincide/relate with the faster updating that WM_TIMER achieves is the simplest route. From my perspective, I just want to be able to control SC to update as quickly as possible, for what I determine is necessary for my charts/quote boards, within the IO capability/capacity of my particular PC. In other words, I want to easily be able to tune SC to achieve the best balance of freshest/quickest data and least amount of CPU usage/fastest UI response time. And I would suggest that SC out of the box settings be set conservatively so that 99% of users/PC specs will have a good user experience with UI responsiveness and fresh data - it probably already is except for the fact that many users may be seeing increased CPU usage even with the default 500ms interval setting because SC is updating more quickly with WM_TIMER. Just my 2 cents, hope it's helpful! |