Support Board
Date/Time: Mon, 20 Jan 2025 13:58:07 +0000
SC 1760 producing "not enough memory" message
View Count: 2347
| [2018-06-08 07:32:18] |
| User44445 - Posts: 3 |
|
The latest version of SC 1760 is producing "no memory" or insufficient memory" errors causing it to close down. My temporary fix was to disable Windows defender and stop my antivirus. This seems to have worked for the moment |
| [2018-06-08 07:59:33] |
| user8888 - Posts: 159 |
|
similar things happens to me. after v1754, getting a lot of 'out of memory' messages, and some other errors and are way slower to load the everyday chartbooks that load fine and fast with 1754. a chartbook that loads in less tan 30 seconds in v1754 might take 6-8 minutes, or more, to load in the new releases, like 1758/1759/1760. |
| [2018-06-08 09:45:24] |
| |
|
a chartbook that loads in less tan 30 seconds in v1754 might take 6-8 minutes, or more, to load in the new releases, like 1758/1759/1760. We did a comparison with version 1750 and 1761. 1760 loading 60 days of ES June data with volume at price data: 8 seconds. 1750 loading 60 days of ES June data with volume at price data: 8 seconds. It is impossible there is any difference with chart data loading because nothing has changed in this regard. What it actually demonstrates is that your system is not running optimally. 1760: TPO profile chart calculation time: 58 ms 1750: TPO profile chart calculation time 50 ms Not sure about the longer calculation time, but this is relatively small and if anything we would expect it would be faster. But there is nothing like what you are describing at all. In regards to memory use, there really should not be much 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: 2018-06-08 10:14:56
|
| [2018-06-08 09:50:22] |
| |
|
Anyway, we will have a look at the memory use issue. That was a problem in one of the releases but it was already solved. The easiest thing to do though is just to use the 64-bit version. There is an icon for it on your desktop.
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-06-08 10:03:53] |
| |
|
We are always very suspicious of these reports because most often in our experience these are system specific issues. We just compared version 1750 memory use with a Chartbook containing nearly 80 charts. Memory use on 1750: 441 MB. On 1760: 442 MB. There is virtually no difference here. While certainly there can be differences in what you are doing that could use more memory than we are seeing in our test, it cannot be drastically different. Furthermore, this Chartbook opens in less than 10 seconds. Anyway, a small adjustment with the new volume container used for volume profiles was made to help with memory use. We have not done any testing with 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-06-08 10:27:14
|
| [2018-06-08 13:51:06] |
| User44445 - Posts: 3 |
|
To put it into context. SC 175X was working fine and has never displayed a memory issue when loading and never closed down by itself. I have made no changes to my system, but when I downloaded 1760 the issue occurred immediately and it was a SC error window
|
| [2018-06-08 18:47:59] |
| |
|
Provide the Chartbook you are using by following these instructions here: https://www.sierrachart.com/index.php?page=PostingInformation.php#AttachFile 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-06-10 04:49:21] |
| user8888 - Posts: 159 |
|
with SC offline, I've got this timings, loading the same chartbook (my heaviest), from an SSD v1754: 1 min 10sec (fine for me) v1761: 4 min I've loaded this chartbook alone. I've got no error messages of any kind. cheers |
| [2018-06-10 06:06:13] |
| |
|
When you say off-line do you mean not connected to the data feed?
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-06-10 06:14:56] |
| user8888 - Posts: 159 |
|
yes sir, that is what I meant.
|
| [2018-06-10 06:30:21] |
| |
|
We are really not sure about this. Check the calculation time of the studies in Analysis >> Studies. Do you notice anything usually larger during real-time updating of charts? If not, then that is not the issue and we can only come to the conclusion that this is a system issue. You have to press the Apply button on the Chart Studies window to get those to update. We are still very suspicious that this is a system specific issue even despite the differences you see between versions. Set Global Settings >> Data/Trade Service Settings >> Advanced >> Intraday File Flush Time to 5000. There are some performance related issues, that we simply just cannot solve because they are system specific. Over the years when these types of issues come up more often than not, there is not really anything that we can do. The only reason we say this is just because when we first saw this, it is just like this doesn't make any sense, and what is this all about. We do acknowledge, that after our initial TPO and Volume profile improvements, one report a very excessive memory use we thought couldn't have been from Sierra Chart but then we realized what the cause was and it was just a simple five second change. 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-06-10 10:57:21
|
| [2018-06-10 07:47:29] |
| user8888 - Posts: 159 |
|
I did the change to that parameter (5000) as you suggested and updated to 1762. I did a fast comparisson of the loading times of some of the studies and just beginning with the profiles you can see some difference. Attached is the chartbook with 1 chart of some profiles and a screenshot of the results of loading this chart in the two SierraCharts I have here. As you can see, takes some more time to load it in a 1762 than it does in a 1754 (and more than doubles the time if you load it in a 1762 64bit) By the way, the 1762 I was using before was a 64bit. The 32bit version is faster loading the chartbooks. v1754 32 bit: 1:10 v1762 32 bit: 2:50 v1762 64 bit: 3:50 Cheers, thank you Date Time Of Last Edit: 2018-06-10 08:10:53
|
Private File Private File |
| [2018-06-10 09:05:27] |
| |
|
We can solve this. We will work on that. We are looking into a solution now.
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-06-10 09:59:27] |
| |
|
We have it solved. We reduced the calculation time by 85%. At first we thought you were referring to the actual chart data loading time. That is different than the study calculation time. 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-06-10 10:00:07
|
| [2018-06-10 10:50:34] |
| user8888 - Posts: 159 |
|
ok, wow!, 85%, that is a LOT. Congrats. Lots of coding talent over there. of course, AFAIK, what delays the most the loading time of the chartbooks, at least in my world full of studies, are the calculations involved. years ago, the processor had to wait for the HDD to load the data. These days is at the contrary. I believe, for most of the people, the loading of the data might not be the biggest issue anymore. To upgrade your disk to an SSD is cheap, fast and easy. To upgrade the CPU is nothing of that. That's exactly my case. aside, please, excuse my english, it is not my native language. I'm trying. While you are working with the profiles, could you please take a look at my previous post titled 'values of TPO & VbP' and at least tell me if it could be possible to make both profiles behave the same, when displaying the values, or not? for simplicity reasons. Congrats again and thank you |
| [2018-06-10 11:10:02] |
| |
|
We are going to have a new release out in about 20 minutes. This will be 1763. It is a prerelease. While you are working with the profiles, could you please take a look at my previous post titled 'values of TPO & VbP' and at least tell me if it could be possible to make both profiles behave the same, when displaying the values, or not? for simplicity reasons. We will get to this as soon as we can.
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-06-10 12:46:58] |
| User20450 - Posts: 330 |
|
glad to see SC helped out people , guess ill get friends to post my request for now on lol .only way it gets done
|
| [2018-06-10 21:48:12] |
| |
|
glad to see SC helped out people , guess ill get friends to post my request for now on lol .only way it gets done We did answer your latest question here and are awaiting a response:1750 up builds !!! We may not have been totally clear about remote assistance. We made our response more clear. 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-06-11 10:45:15] |
| |
|
We have it solved. We reduced the calculation time by 85%.
There still was an outstanding performance issue which has now been resolved . So if you have updated to 1763 update again. We put out a new revision.We are going to be making additional performance improvements and then later today releasing 1764. This should finalize all of the improvements. There has been no changes in regards to memory use. This remains the same. 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-06-11 10:45:17] |
| |
|
We have it solved. We reduced the calculation time by 85%.
There still was an outstanding performance issue which has now been resolved . So if you have updated to 1763, update again. We put out a new revision. And also for the record, what we did to get the 85% reduction and what we did today, is a major improvement. The latest improvement is performing an incremental sort of the volume at price data.We are going to be making additional performance improvements and then later today releasing 1764. This should finalize all of the improvements. There has been no changes in regards to memory use. This remains the same. So in regards to the original post, we do not know what the issue is in your case. We would need to get your Chartbook and then let you know how much memory use we actually observe with it. 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-06-11 10:51:25
|
To post a message in this thread, you need to log in with your Sierra Chart account: