Support Board
Date/Time: Sun, 24 Nov 2024 17:26:52 +0000
Post From: Severe lag on newer versions
| [2023-11-28 06:40:46] |
| Sierra_Chart Engineering - Posts: 17156 |
|
We have done our initial performance comparison between versions. The analysis right now is somewhat crude because we need to to implement averaging of the timings. Testing version 2566 against version 2480 (From February 2023) using a Chartbook with the Chart DOM, displaying 100 levels of depth, pulling and stacking data, one study, candlestick bars, with no bar spacing, so a lot of dense graphics, 2566 roughly is like 10% faster but we have not done the exact math. It is certainly not slower. So there certainly is no severe lag at all. This is just simply not correct. It is the opposite. Newer versions are delivering higher performance. So what we said at the beginning of the thread absolutely is correct: Severe lag on newer versions | Post: 362332 Definitely we believe that the issue that some users are having is system specific. For whatever reason, your system is just simply not efficiently running Sierra Chart. Power management may be a significant contributor to this. It is not enough to make operating system changes. You have to go into your system BIOS and disable all of the power saving features. Here is more information on P and C states: https://www.intel.com/content/www/us/en/docs/vtune-profiler/user-guide/2023-0/window-cpu-c-p-states-platform-power-analysis.html One of our developers was saying, than a more efficient program, can be allocated to a lower power core, and then run more poorly as compared to a less efficient program. It could be that due to Sierra Chart's high-efficiency that it is not running on a core running at a high clock speed and every time there is a need for more processing power, it takes time for the CPU to clock up which is causing the lag. You want to get your power management on the computer to a point where when you look at the Task Manager you do not see the CPU frequency changing. It should be locked above the maximum clock speed. It will be above the maximum clock, due to the turbo feature of CPUs. We are not recommending that you always keep your CPU in this state. But it is a good experiment to evaluate the problem. Warning: Please be careful with what we say. We do not want to cause users problems with CPU overheating although they should turn off if there is a serious problem. Maybe it is best to make more moderate adjustments, in order to diagnose the problem. With our servers, we do keep the CPUs at the maximum speed as we previously described, and they do generate a significant amount of heat. And there is more power consumption and heat generation. Ultimately what the problem is, we cannot say for sure. But one thing we are certain of is there is not a performance degradation in newer versions. It is the opposite. There is an improvement or it is the same. We will have more information once we implement the averaging. And this will be released as a feature that you can use. The only other thing we did not measure is network I/O but there is no point in that because nothing has changed with this, and this already has an extreme high-performance implementation which is used in our servers, handling massive massive amounts of more data compared to users. The data feed processing also has not changed and is exceptionally fast. These two categories of processing, run on separate threads. Newer versions of Sierra Chart do have a significant amount of more threads. We will see what that is about. Perhaps that is causing the problem. But it should not. And if there is a problem in your case from this, once again it probably relates to power management. These threads are in a wait state. In any case, we are going to be looking into this. Another thing you can do, is set this setting to 10000 or higher: Advanced Service Settings: Intraday File Flush Time in Milliseconds (Global Settings >> Advanced Service Settings >> Other) So in conclusion, there is nothing for us to be doing other than to look into the additional threads. These versions are delivering higher performance. You need to resolve the problem on your side. And even thinking about this some more, the performance timing functionality that we will be offering, can be totally misleading because if your system is causing Sierra Chart to run more slowly, then you will see higher timings and attributing it to a particular version when the version was never the problem to begin with, instead it was your hardware. Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, use the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2023-11-28 08:23:06
|