Support Board
Support Board
Search Board
Control Panel
View My Posts / Threads
Direct MessagesDate/Time: Wed, 24 Apr 2024 18:31:03 +0000
Rising CPU and other issues Version 1787 Onward
View Count: 1777
| [2018-09-05 02:13:37] |
| User379884 - Posts: 45 |
|
Hi, Today I went from 1784 to 1795. I noticed the following issues. - By 1015am NY time my CPU for SC had risen to over 12% and the charts were updating very slowly. - Minor issue but the bid and ask lines on the chart were both red despite both the global graphic settings and the individual chart settings being red and green. No matter what I did I could not change them off both being red. I rolled back a number of times to prior versions (I can't recall which ones) till I got back to 1784. Both issues persisted until I was back on 1784. My chart book is very simple. I have 6 charts (only two visible at any one time), 5 with update intervals of 500ms and one with 175ms, few indicators, minimal chart drawings (a few horizontal lines). I use SC data with the advanced CTS connection. When on version 1784 my CPU for SC ranges between 2%-3.5% depending on the volume of the day. I am happy to sit on 1784 but thought I would raise this to let you know. |
| [2018-09-05 02:37:42] |
| |
|
Well as far as CPU usage goes, we are not aware of any problems and we would expect it to be less. Perhaps the issue is graphics related and we might know what the cause is if this is the case. If you look at the Windows Task Manager when you notice this problem look at the GDI Count for the Sierra Chart process. Let us know what you see. Update: really the GDI object count is the only area we are aware of where there could be a potential problem but we made certain this should not be a problem and we had a look at the code and really it should not be a problem , so we are not sure what the issue is. Are you using any custom studies? - Minor issue but the bid and ask lines on the chart were both red despite both the global graphic settings and the individual chart settings being red and green. No matter what I did I could not change them off both being red. This has already been resolved.
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, *change* to the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2018-09-05 03:38:56
|
| [2018-09-05 03:20:50] |
| |
|
Provide the Chartbook you are using and we will test it for a day and see what we notice. This is really going to be the only way for us to observe what the issue is and what we need to do to resolve, assuming it is an issue on our side. Here are instructions: https://www.sierrachart.com/index.php?page=PostingInformation.php#AttachFile Please do provide this as soon as possible so we can look into the issue. 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, *change* to the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2018-09-05 03:30:38
|
| [2018-09-05 03:33:19] |
| User379884 - Posts: 45 |
|
Hi, Please find attached. |
Private File |
| [2018-09-05 03:37:43] |
| |
|
Okay thank you. We will set this up for a test.
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, *change* to the Teton service: Sierra Chart Teton Futures Order Routing |
| [2018-09-06 03:43:07] |
| User379884 - Posts: 45 |
|
Is there any way to know what version I was originally on, like is there a log of the versions I have used? Issues I had with V1784 in the CME session just gone; - continued to have performance issues with lagging charts right from the open. Whilst I know it was a high volume session, there was a similar session 2 weeks ago where the version I was using had no issues. My CPU was not going above 4% so it was ok. - I selected the option "delete and downloaded data" as a possible fix. It was taking around 30 seconds to load each day. I exited and rolled back to 1781 and it loaded 3 months in around 45 seconds. - I still continued to have lagging charts with V1781 with what looked like a refresh rate well above 500ms. I upped my refresh rate to 250ms on my execution chart which still did not seem to work. As an example trades I made were reporting the target as being filled before the candle was being drawn. I had a prior issue with lagging charts sometime ago so am familiar with the troubleshooting for these. In that instance it was a custom study I had which I no longer use for that reason. I have all of these issues screen recorded if you need to see any of these issues. Ultimately if possible, I would like to know what version I upgraded from on Monday evening EST as before then I was having no issues. If there is a way to find this out it would be greatly appreciated. |
| [2018-09-06 04:19:55] |
| |
|
For the record, we see no issues at all using your Chartbook. CPU usage remains at 0%. GDI object count is low. Memory usage is low. Nothing unusual. And it has been running nearly a day now on a 64-bit release build. We will continue to monitor for another two days. The global Chart Update Interval is set to 200 ms. We also tried a replay at 240 times, CPU usage is 0%. There is nothing inefficient going on at all. The only record of a previous version you would have been using is if you have Global Settings >> General Settings >> General 2 >> Save Message Log to File enabled. We believe this is a system specific issue. We are intimately familiar of the development we have done in Sierra Chart, and the only area of concern would be Spreadsheets and graphics. There is no evidence at all of a graphics issue and we would not expect that. And you are not using spreadsheets. 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, *change* to the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2018-09-06 04:36:00
|
| [2018-09-06 04:40:53] |
| |
|
We are doing a 960 times replay now of all of the charts in the Chartbook and CPU usage is at 1%. The Chartbook is very active and this is after Sierra Chart has been running nearly 24-hours. Our only conclusion here is that this is a system issue on your side. And this is with tick by tick data in the Intraday chart data files. 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, *change* to the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2018-09-06 05:23:43
|
| [2018-09-06 05:30:49] |
| |
|
Attached are the specifications of the system Sierra Chart is running on with your Chartbook. Also there is no system security software which has any effect on Sierra Chart on this particular system. Reference: https://ark.intel.com/products/75266/Intel-Xeon-Processor-E5-2470-v2-25M-Cache-2_40-GHz Although this is a 10 core CPU, after the chart books are loaded, only about 3 cores/threads would be in active use by Sierra Chart. And only one of those threads would be significantly active . The processing on the others is generally minimal. One is used for network I/O another one is used for Intraday data file writing. The primary thread is handling graphics, and chart calculations. 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, *change* to the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2018-09-06 05:35:20
|
 2018-09-05_222812.png / V - Attached On 2018-09-06 05:30:36 UTC - Size: 9.03 KB - 334 views |
| [2018-09-06 20:22:22] |
| |
|
Your Chartbook continues to run at 0% even when the market is active. We definitively believe this is going to be a system issue on your side especially being you say you progressively notice higher load over time. The memory usage is under 100 MB and the GDI object count is 280 which is low and that is nowhere even remotely close to an area where there could be a problem. There would have to be a GDI object count in the thousands for there to be a potential problem.
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, *change* to the Teton service: Sierra Chart Teton Futures Order Routing |
| [2018-09-06 23:29:03] |
| User379884 - Posts: 45 |
|
Thank you for the extensive testing. Yesterday I upgraded to 1798. SC performed perfectly. It was also the hishest volume session since earlier in the year where one might forgive some performance issues, and there certainly wasn’t. It was rock solid. Again thank you for your effort to resolve it. I’m glad it’s back to it’s usual rock solid self. |
| [2018-09-06 23:37:19] |
| |
|
We did not change anything or resolve anything, related to this. We still definitely believe that this was a system related issue. That is the only logical explanation. And we do have a lot of experience with this. The only thing changed was to Spreadsheets and this is in prerelease 1799 or still has yet to be released. 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, *change* to the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2018-09-07 00:17:17
|
| [2018-09-08 02:08:01] |
| |
|
Apparently the issue is a GDI object count which is too high. Another user is experiencing this: CPU usage & GDI count V1798 So if that is it, then this is something we need to look into and it would seem like you could have the problem again because it would seem to be intermittent. There is nothing we have changed to our knowledge which would have resolved this. And we also could not reproduce it either. 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, *change* to the Teton service: Sierra Chart Teton Futures Order Routing |
| [2018-09-08 03:57:30] |
| User379884 - Posts: 45 |
|
Thank you for the update. As posted in the thread you linked would you recommend rolling back to 1781? Or is there another version you recommend? |
| [2018-09-08 20:50:46] |
| |
|
Stay on the version you are and then if you have a problem check the GDI Object count in the Windows Task Manager for the SierraChart.exe process and let us know what it is.
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, *change* to the Teton service: Sierra Chart Teton Futures Order Routing |
| [2018-09-10 07:17:13] |
| |
|
The GDI object leak has been resolved in version 1802. It is the result of the development to move all of the graphics related code into a common component and there was a certain scenario in one case where a device context was not getting deleted.
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, *change* to the Teton service: Sierra Chart Teton Futures Order Routing |
| [2018-09-10 07:35:48] |
| User379884 - Posts: 45 |
|
Greatly appreciated getting this issue resolved so quickly.
|
To post a message in this thread, you need to log in with your Sierra Chart account: