Support Board
Date/Time: Tue, 26 Nov 2024 00:42:14 +0000
Performance drawdown with version 2576 and higher (DOM and Charts)
View Count: 2658
| [2024-01-08 11:32:28] |
| User61168 - Posts: 403 |
|
Offloaded more than 100 charts instead of running a new instance, try a new second install (new directory structure) to see if it makes any difference and then slowly scale up the number of chartbooks one at a time.
|
| [2024-01-19 05:21:47] |
| Sierra_Chart Engineering - Posts: 17178 |
|
This is not really true: Now they implemented performance changes which have slow down the platform.
There really are no fundamental changes, which would have any major performance impact for the better and certainly not for worse. Little performance improvements are done here and there, but they are generally going to be undetectable and not even worth mentioning. Offloaded more than 100 charts to subinstance and started both instances in safe mode. 2580 still shows lag when entering orders in DOM compared to 2550.
What we want to say regarding this, is that if you have a lot of charts open which clearly you do, you need to determine what is the average calculation/draw time of these charts. The calculation time also varies, whether the charts are visible or not. If they are visible, the higher the calculation/draw time.Let's say, each chart takes 10 ms for calculation and drawing. And you have 1000 charts. This means it is going to take 10 seconds to calculate/draw them all. So the Global Chart Update Interval needs to be 10000 milliseconds. And then for charts, which need to be updating faster you can set the update interval specifically for those to 100 ms. You would only want to do this for a handful of charts or Trading DOMs. To help you analyze all of this, in the latest version, under Chart >> Chart Settings >> Performance there is a new field called the Average Calculation and Draw Time. It is implemented in a much more precise way than the other fields of information on that tab. This new field is much better. You are going to want to have a look at this field, when a chart is visible and not visible. You can open the chart settings window for a chart, and then maximize another chart while the chart settings window is open to make the current chart not visible. And you will see the CPU usage drop on it. It may go to 0 ms. Now if you are still having a significant problem you must look at your system as the cause. Because your system is executing a newer version in a more detrimental way and why that is the case we do not know. We have put forth various suggestions, including power management . Whether this is a factor or not. We do not know. But there can be all kinds of odd things which can go on, in complex computer systems for reasons which are not obvious. Security software can be impacting the software and the system. You are going to have to figure this out. But one thing is for certain is Sierra Chart is fine and executes very very fast. 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: 2024-01-19 05:25:31
|
| [2024-01-19 07:56:33] |
| User889191 - Posts: 61 |
|
The point is this: Version 2550 with my computer system performs extremely fast. No issues. This is Sierra Chart as I know it for years. By the way, in my chart count in one of my previous posts, I not even mentioned additional dozens of charts that run already in background. They are hidden to reduce resource consumption. All works fine. I repeat it again for Sierra Chart Engineers: It works absolutely fine. It performs like hell → Well done ! Version 2580 with exact same computer system (no changes at environment e.g. windows, CPU, network etc.). I only update Sierra Chart. Then I see performance slowdown. E.g. Order Entry is deferred. If I click on DOM to enter order, it is slower. I can see it easily. Some change between 2550 and higher version is the root cause of this. Which higher version exactly causes this behavior I cannot tell. Please check changes that have been implemented. Sierra Chart is suspicious because nothing else changed. Thank you. |
| [2024-01-19 08:25:13] |
| Sierra_Chart Engineering - Posts: 17178 |
|
There is absolutely no problem we would find. We cannot reproduce any issue like this. There were no changes that could cause a problem and we would never find anything. There is no issue that we would ever be able to find. And there is not a problem. The issue must be something specific to your system. This is why we raise the power management possibility.
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: 2024-01-19 08:47:50
|
To post a message in this thread, you need to log in with your Sierra Chart account: