Support Board
Support Board
Search Board
Control Panel
View My Posts / Threads
Direct MessagesDate/Time: Thu, 25 Apr 2024 17:16:42 +0000
CPU usage & GDI count V1798
View Count: 2259
| [2018-09-07 16:26:25] |
| User907968 - Posts: 802 |
|
Hi support, For me, V1798 seems to be causing higher CPU usage and possibly there is a GDI leak. After the software has been running for a few hours I notice a couple of things will occasionally happen - 1) there are times when the charts lag behind the data I see on my standalone DOM's, sometimes a 1-2 seconds, sometime 20-30 seconds 2) the application will randomly hang for anything from 5-30 seconds, 3) there will be some graphic glitches (e.g. charts flickering, charts not displaying a quickly as normal when switching chartbooks) I've not experienced either 2 or 3 before (as far as I can remember anyway...), I have noticed item 1 but this was generally only in very fast moving markets. I've been through help topic 30, but my chartbooks are largely unchanged for quite some time, so I didn't see the benefit in making too many changes until I understand the issue. Regarding the possible GDI leak - V1781 was the last version that had a stable GDI count (typically 1200 +/- 50). V1798 starts out with a similar count, but this increases all the time the software is running, yesterday it started at around 1150 and at the last time I checked it, it was near 5000. I don't know if this is normal or to be expected, but I thought I should make you aware. It may be that there is something wrong at my end (e.g. bogus windows update), but I don't believe this to be the case. Thanks for your help. |
| [2018-09-07 16:57:35] |
| |
|
That GDI Count is too high and that is a problem. Even a 1000 is high. We need to be able to understand the cause and reproduce it. If this happens with one particular Chartbook we need you to attach that Chartbook by following these instructions here: https://www.sierrachart.com/index.php?page=PostingInformation.php#AttachFile See if you can isolate the problem down to one Chartbook. 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-07 18:41:03] |
| User907968 - Posts: 802 |
|
Hi, thanks for the prompt response. I will investigate over the weekend to see if this can be isolated to one particular chartbook, but as they are all pretty much exactly the same setup (just different symbols), I would be surprised if I am able to narrow it down. |
| [2018-09-08 12:43:23] |
| User907968 - Posts: 802 |
|
I have done some testing with each chartbook individually using replay mode but not have been able to recreate the issues described above, I will repeat the excercise on Monday with live data. For each individual chartbook the GDI count seems stable in the 450-500 range, is this more in line with what you would expect? Some additional observations of interactions that cause the GDI count to increase in v1798, but not in v1781 - 1) Switching between chartbooks (when multiple chartbooks are open) 2) Switching between (and then using) the crosshair and any of the drawing tools (or vice-versa) 3) Selecting and deleting drawing objects (using the delete key and then clicking on the object causes a greater increase than deleting the object via the context menu) Apoogies if the behaviour listed is expected. Hopefully I can come back to you with more information early next week. |
| [2018-09-08 23:18:50] |
| |
|
Yes under 500 would make sense. Provide that Chartbook and then we will test it doing these items you mentioned. 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-09 05:25:51] |
| |
|
We do see the GDI Object count increase merely by selecting a different Drawing Tool. We are going to look at it. So no need to provide anything more at this point. Once we find that and resolve, that probably is the underlying 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 |
| [2018-09-10 07:16:04] |
| |
|
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 Date Time Of Last Edit: 2018-09-10 07:16:49
|
| [2018-09-13 16:23:10] |
| User907968 - Posts: 802 |
|
Hi support, I am not sure whether I should start a new thread or continue this one. The GDI leak seems fixed but, the last 3 days (today and yesterday particularly) I am still intermittently experiencing issues 1 & 2 from the original post. I have been through help topic 30 and help topic 4, so far I don't believe there to be a problem with the data delivery, but instead possibly data processing at my end. NOTE - the issues only present in the instance of SC that is used with tick-by-tick futures data, I have not noticed problems with a separate instance used for FX data with 5 second data storage time unit. To my knowledge there have been no changes at my end, aside from windows updates, updating Sierra Chart and following the suggestions in topic 30 to make chartbooks more efficient. I don't really understand why the recent issues have arisen for me, but would really like to find a solution. Can you make any suggestions at all? Should I roll back to an earlier version of sierra? Should I upgrade my hardware (currently running win 7, i7-4790k, 32gb ram, 2 instances of Sierra on separate SSDs)? Could I be doing something wrong that can easily be remedied? |
| [2018-09-14 01:49:05] |
| |
|
We recommend using more instances of Sierra Chart. Refer to: Using DTC Server for Data and Trading in Another Sierra Chart Instance To whatever extent this relates to the GDI object count, you can probably tell just by looking at that count. It should not really be more than 500. If it is, we will have a new release out which may help with this, in a day or two. Ultimately these issues are going to be system-level issues and operating system level issues. Especially something like this: 3) there will be some graphic glitches (e.g. charts flickering, charts not displaying a quickly as normal when switching chartbooks)
We do acknowledge the GDI object leak, which has been definitively resolved, but all other performance related issues, ultimately are due to limited hardware, the configuration of Sierra Chart including your charts, and inefficiencies at the operating system level. There is only so much we can do to help with those. You simply have to get more capable hardware and use more instances of Sierra Chart if you are pushing the limits of what a single process of Sierra Chart can handle based upon what you are doing, and what the operating system can handle. 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-14 01:49:55
|
| [2018-09-14 07:51:26] |
| User907968 - Posts: 802 |
|
Hi, Thanks for taking the time to reply again. Re the GDI issue: - Certainly the leak seemed resolved in latest version, since which I had not once noticed the graphics issues described. - The object count is still >500, typically I see 600-800 depending on how many chartbooks are open (or 1000-1400 if 'destroy chart windows when hidden' is not enabled) Re the general performance: I understand that you can only offer limited help, what with there being so many possible variables (the vast majority being completely beyond your control), I also take on board your advice re hardware upgrade and/or more instances of Sierra Chart, however: - Typical average CPU load for SC is in the 3-7% range - this does not seem too high - Detached charts are listed as a possible problem in another support board thread - I do have quite a few detached charts, but this has been the case for >18 months - I still believe that the issues that I see are a recent phenomenon, despite my efforts to make my chartbooks more efficient - I have reverted back to an earlier version, as I would like to test for myself before reorganising my chart setups or upgrading my hardware If upgrading my system turns out to be the right option for me, could you offer some basic advice please? - Do I need to move away from Win 7? - What will be most beneficial for SC performance: more processor cores, higher single core performance, higher multi-core performance, more memory, all of the above? Sorry if I am wasting your time or if my questions are beyond the scope of support. |
| [2018-09-14 09:37:36] |
| |
|
We are not giving up on this, but the basic point is, that the very fact that such a problem is arising with something as trivial as even a 1000 GDI objects is completely ridiculous and it really just speaks very poorly of the Windows operating system. Based on everything we are reading here and knowing what changes have been done, all evidence is that this is strictly a graphics related issue. And the graphics performance in Sierra Chart has been greatly improved upon but the fault really lies at the OS level and that is where we are trying to come up with some kind of solution. We are going to have a new release out in a few hours, that removes the GDI object pool, and we will want you to test that. A lot of work went into that GDI object pool by a very experienced developer, and it is ultrafast and it is very sad that the Windows OS is performing massively poorly with it. Also when we add support for Open GL this will be a solution as well. As we have said elsewhere, the more time that goes by and the more that we develop more functionality ourselves and remove independence from the Windows OS, we clearly realize just how substandard and inefficient the Windows operating system really is. How Microsoft is gotten so big powerful and wealthy off of substandard software is beyond belief. In general every new release of Sierra Chart is faster than the release before. We are quite certain though the detrimental performance, is at the OS level which we are able to work around. The OpenGL support should be a major leap forward. And we are currently working on this now. It remains a high priority for us. 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-14 09:45:41
|
| [2018-09-14 10:04:12] |
| User907968 - Posts: 802 |
|
Ok, thanks again for your continued support. Happy to test updated release, please advise once it is ready. |
| [2018-09-14 17:57:18] |
| |
|
We have released 1805. We want you to test on that version and see if it resolves the performance issue you are having.
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-14 19:33:29] |
| User907968 - Posts: 802 |
|
Thank you, will test over the weekend and/or Monday and report back.
|
| [2018-09-15 23:04:07] |
| ertrader - Posts: 644 |
|
The OpenGL support should be a major leap forward. And we are currently working on this now. It remains a high priority for us. I do understand you do not currently support Linux with Wine. However, do you have any information on running OpenGL on Wine? Linux with Wine is my primary trading operating system and want to ensure SC continues to work well. Currently SC works exceptionally well with Wine. I'm also thinking a move to OpenGL will greatly help if a Linux version becomes available in the future. Date Time Of Last Edit: 2018-09-15 23:10:22
|
| [2018-09-15 23:17:27] |
| |
|
Thank you, will test over the weekend and/or Monday and report back. Actually if you could just wait until we have 1806 out that would be better. We want to do some additional testing. However, do you have any information on running OpenGL on Wine? Not at this time. But I am sure we will have more information later on as this project progresses.
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-17 15:49:31] |
| User907968 - Posts: 802 |
|
Hi support, v1806 seems to be a big improvement, albeit after only fairly limited testing at my end. SC seems much more responsive in general and so far no evidence of lagging or application hanging. Thanks |
| [2018-09-17 16:47:54] |
| |
|
Clearly the operating system is having a problem with a high GDI count. Clearly that is not good. It really is a big joke. There are numerous ways the operating system can optimize the lookups. It really just goes to show the pathetic nature of Microsoft and the Windows OS. To what extent the caching within Sierra Chart is contributing to the problem with the time to look up GDI objects we would have to evaluate. But we do know with certainty, the majority of the problem is on the OS side. Another interesting thing is look at the programs running on your system that have a high GDI count, and how their performance is impacted. We have noticed Chrome has a high GDI object count. And the Windows Explorer does as well. And Microsoft is incapable of solving this? It is completely ridiculous. 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-17 16:54:32
|
| [2018-09-18 08:56:44] |
| User907968 - Posts: 802 |
|
Another interesting thing is look at the programs running on your system that have a high GDI count, and how their performance is impacted. We have noticed Chrome has a high GDI object count. And the Windows Explorer does as well. And Microsoft is incapable of solving this? It is completely ridiculous.
Interesting, so there is no escaping from the issue at an OS level? Is there any benefit to upgrading from win7, or do the same issues persist in win10 (which version do you use)? |
| [2018-09-18 13:05:14] |
| |
|
We do not think there is any benefit in updating.
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-18 13:24:28] |
| User907968 - Posts: 802 |
|
Thanks for the advice, very useful as I certainly wasn't overly keen on updating.
|
| [2018-09-20 15:49:47] |
| User907968 - Posts: 802 |
|
Hi Support, Just an fyi, V1809 seems to have yielded a huge improvement in overall performance, so whatever you have changed, it is definitely working for me. Many thanks for your continued development efforts. |
| [2018-09-20 19:27:39] |
| |
|
Very simply, geometric pens consume a lot of CPU time at the operating system level. Not using these pen types for lines with a width of 1 is what has changed. Using a geometric pen in that case was inadvertently happening in a recent version. Also not using the Alternate style , but we still need to evaluate the effect of the Alternate style when we have a chance next week. So none of the CPU load was from Sierra Chart itself, it was all at the OS level related to pens. 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-20 19:30:03
|
To post a message in this thread, you need to log in with your Sierra Chart account: