Login Page - Create Account

Support Board


Date/Time: Thu, 27 Feb 2025 06:59:59 +0000



Performance Issue 2253 and 2260

View Count: 1594

[2021-05-19 21:04:11]
User656492 - Posts: 146
I just installed SC on a new computer. It took ver. 2253 as default. Friends have complained that this version is a performance hog and I know that there's a pre-release version of 2260. THIS DOES NOT SOLVE THE ISSUE.

My new machine is a 6 core i7 with 32gb ram. Right now, with market closed, and data disconnected, Task Manager is showing 12.5% CPU usage.

My old machine, an old i5 with 16gb is showing 3% with the same chartbook loaded AND connected to data.

You folks have an issue.
Date Time Of Last Edit: 2021-05-19 21:05:09
[2021-05-19 21:12:46]
User656492 - Posts: 146
After some experimentation, it appears that performance is directly impacted by the size of the master SC window. CPU utilization drops dramatically when reducing the window size, even with market closed. What I don't understand is why this is all on the CPU and zero load on the graphics card... ?
[2021-05-19 21:50:39]
User656492 - Posts: 146
Another update - I have a footprint / numbers bar chart with various studies. This one chart appears to be responsible for all the CPU usage. Will provide more info when I dial it in.
[2021-05-20 01:44:06]
user_xyz - Posts: 446
Possibly related I've been going through these one by one as I've noticed higher CPU usage as well but wasn't sure if it was the latest release or possibly I changed/added study that is causing it.

High CPU Usage | Inactive User Interface | Poor Performance | Long Time to Load Chart Data | Charts Reloading Often
[2021-05-20 21:22:32]
User656492 - Posts: 146
I believe I've figured out the problem. Sierra was using 30% of a 6GB GPU and 15% of (presumably 1 core of my 6 core CPU) while using opengl. This GPU & CPU usage drops immensely when the footprint (numbers bars) chart is hidden. After consulting with other friends who use SC (we talk to each other, in case this wasn't obvious) I reviewed chart references and found that the power consumption was caused by references to another chart. The 5 minute footprint chart was referencing drawings another 5 minute candle chart and a 30 minute TPO chart. The cause of the problem was the drawings references from ..... the other 5 minute chart.

SC - this is an issue.

For what it's worth, this is also true for version 2253, 2258, 2260 - maybe older but I'm only now looking to solve it.

Machine:

Graphics Card: NVIDIA GeForce GTX 1660Ti 6GB GDDR6
Processor: 10th Gen Intel Comet Lake Core i7-10750H Six Core ( 2.6GH z- 5.0GH z, 12MB Intel Smart Cache, 45W)
RAM: 32GB
[2021-05-20 21:36:58]
User656492 - Posts: 146
Look into diagonal lines.
[2021-05-20 22:41:45]
user_xyz - Posts: 446
I'll try and get back researching this tonight.. I have a similar setup with a daily chart that TPO and 5 min charts reference drawings and other settings on it. No diagonal lines but I have horizontal ones.
[2021-05-20 23:55:03]
Sierra Chart Engineering - Posts: 104368
How many drawings are being copied from a source chart? And are these text drawings?

There was a minor change involving the displaying of text drawings added by ACSIL and when a bar index is specified for the horizontal coordinate. But very minor. Nothing that should cause any increased CPU usage.
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: 2021-05-20 23:55:43
[2021-05-21 00:18:00]
User656492 - Posts: 146
This isn't the entire problem, but it did make a difference. At 5:17pm PDT, my GPU is currently bouncing between 20 and 30% utilization. But this is way too much. I'm pretty sure I could be playing some pretty amazing video games that use less GPU power.
[2021-05-21 00:20:14]
Sierra Chart Engineering - Posts: 104368
The only reasonable explanation for an issue like this is that there is a detection that the Chart Drawings in one or more source charts are being detected as being changed, when they actually are not, causing the destination chart to continuously redraw at the Chart Update Interval. If you are using a very low chart update interval, then that significantly increases CPU usage.

So we need to look into that.

This would also mean that when you disconnect from the data feed with File >> Disconnect, that it makes very little difference.
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: 2021-05-21 00:20:37
[2021-05-21 01:27:41]
User656492 - Posts: 146
disconnecting the data feed took the numbers down, but not to zero.

I hid the Realtime Clock study to make sure nothing is being updated.

I'm seeing "moderate" CPU and GPU usage. 4% and 8%. This is version 2253.
[2021-05-21 05:29:05]
Sierra Chart Engineering - Posts: 104368
Regarding post #10, this is an issue for certain types of Chart Drawings like Ray drawings and we have implemented a solution. This will be out in 2261.

This is nothing new though. This issue would have had to exist for a very long time. How long we do not know. It would be at least a year. However, if it solves the issue that is good.
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: 2021-05-21 05:29:57
[2021-05-21 05:43:13]
user_xyz - Posts: 446
Ah good to know. I recently added a few ray drawings and that coincides with about when I noticed the ramp in cpu utilization. I have TPO, number bar, footprint, shared rays, shared lines, shared vwap, shared pivots. I'll test in the am.

FYI No shared text drawings.
Date Time Of Last Edit: 2021-05-21 05:44:12
[2021-05-21 13:23:03]
Sierra Chart Engineering - Posts: 104368
We have released version 2261.
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
[2021-05-21 16:30:43]
user_xyz - Posts: 446
To reduce variables - I updated to 2261 before making any changes and my CPU is still high.

I did notice on my daily chart pivots appear to be redrawing with every tick. There is a small movement/shift in the lines.

I'll update this post but going to start going through everything to try and locate the issue.
Date Time Of Last Edit: 2021-05-21 16:34:30
imagePivot.png / V - Attached On 2021-05-21 16:32:52 UTC - Size: 48.07 KB - 200 views
[2021-05-21 18:25:51]
ertrader - Posts: 681
Not sure if this is related but I'm seeing much higher memory usage in 2258. 1.1-1.9 Gig. It is usually 300-400K. CPU usage is normal...4-5%

I'll do some work on my end to see if anything else could be causing higher memory usage. I do not use any text drawings.
[2021-05-21 18:54:58]
Sierra Chart Engineering - Posts: 104368
No the memory issue is not related at all, and this is not going to be a Sierra Chart issue 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
Date Time Of Last Edit: 2021-05-21 18:55:10
[2021-05-21 21:06:47]
Sierra Chart Engineering - Posts: 104368
We really need to get a test Chartbook, preferably as simple as possible, from someone and we need to test on an earlier version and the current versions and see if we can isolate where the difference is. Although this in itself, is very very involved.
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
[2021-05-21 21:57:55]
user_xyz - Posts: 446
Here's one. As a test I wanted to load up a simple chartbook with 4 charts and the CPU went to 6% and stayed there, switching back to my more complex main chartbook didn't lower it. FYI - These charts reference a spreadsheet study which according to 30.2 I reduced the rows to 1000.

I'm trying to systematically go through each of theses to identify High CPU Usage | Inactive User Interface | Poor Performance | Long Time to Load Chart Data | Charts Reloading Often as I feel it's a study, or a setting that I added/changed that's causing this (in my case)

Actually here's both. If I open both chartbooks and switch back and forth the cursor hangs for a few seconds and everything is laggy. I need to close the print.cht to get back to a decent state.
Date Time Of Last Edit: 2021-05-21 22:08:47
Private File
Private File
[2021-05-22 03:25:23]
User656492 - Posts: 146
2261 is MUCH better!
[2021-05-23 19:17:36]
user_xyz - Posts: 446
#1 - of my performance hits is definitely related to the spreadsheet study. When I open up a second chartbook (print.cht) it has 4 charts referencing the spreadsheet study (set to 1000 rows) and SC cpu spikes and becomes really laggy (waiting 2-4 seconds during clicks). Right now it's the weekend/AH so no data is coming in and still hanging.

Maybe you can't have different chartbooks reference a spreadsheet study? Thoughts?

20210524 - Found the problem with the spreadsheet study here, referencing a spreadsheet from two open Chartbooks is going to put the CPU into overdrive. -> Spreadsheet Study Inputs: Number of Rows


#2 - Related to pivots redrawing continuously. See the attached video and screenshot of the settings. I'm sure it's a setting somewhere but the chart in the video is set to reference another chart for daily so I believe it shouldn't fluctuate, it should be a constant value, not continuously redrawing.
Date Time Of Last Edit: 2021-05-25 05:24:16
Private File
Private File
[2021-05-23 20:33:59]
ertrader - Posts: 681
Yes...agreed on post #20 above. Memory usage is back to normal after updating to V2261. CPU % is back down to 3-4%. Memory usage 515Meg.
Date Time Of Last Edit: 2021-05-23 20:34:18
[2021-05-24 21:39:46]
user_xyz - Posts: 446
Any thoughts on post #21.

Also does anyone know how to monitor CPU usage for a child window in SC? Task manager and sysinternals process explorer just show the parent SC app. I thought someone/somewhere was able to track high CPU usage to a specific chart (which would be super helpful)?
[2021-05-25 05:37:43]
Sierra_Chart Engineering - Posts: 18584
. Memory usage is back to normal after updating to V2261
Regarding this. This is what we previously said:
No the memory issue is not related at all, and this is not going to be a Sierra Chart issue either.

That is 100% accurate. We never changed anything regarding memory usage. This was never a Sierra Chart issue at all. So you can see why we are very adamant about these claims that these are just not Sierra Chart issues. And you should also understand that the way that operating systems manage memory, that there can be very wide ranging fluctuations with memory usage which is outside the control of the program.
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
[2021-05-25 07:01:33]
Ackin - Posts: 1865
So you can see why we are very adamant about these claims that these are just not Sierra Chart issues.

By changing some features within Sierrachart version 2258,2259,2260, the operating system of some users responds differently (more workload).

For me, version 2261+ is also better (and thank you for that) and now it works just like the 2248 version which has long been used as stable for me.... versions 2253-2258 were a disaster. It increases the system load by 10-25 percent ... for me (same computer, same studies, same charts), someone else can be without problems ....

That's just feedback....
Date Time Of Last Edit: 2021-05-25 07:03:26

To post a message in this thread, you need to log in with your Sierra Chart account:

Login

Login Page - Create Account