Support Board
Support Board
Search Board
Control Panel
View My Posts / Threads
Direct MessagesDate/Time: Sat, 20 Apr 2024 12:11:15 +0000
[Locked] - Version 1836: Critical/Performance Improvements
View Count: 696
| [2018-11-05 08:55:07] |
| |
|
Version 1836 has now been released. It is a pre-release at this time. It has the following what are considered critical and performance improvements. - Recently there were performance improvements With volume and TPO profiles. Part of that development though also introduced a less efficient method of accessing a particular Volume/TPO profile within the chart. At the time this was not considered to be a problem but it is an issue when there is a huge number of volume profiles in the chart like tens of thousands of them. We have now implemented an ultrafast access method. We think this issue has been the reason why sometimes when a user open a Chartbook, Sierra Chart freezes for an extended time. It could be based on the fact that there is a huge number of volume profiles in one or more of the charts. This should no longer cause a problem. - In various areas of the program there are lookups of symbol settings. This can be the case in the orders list, and also the trade activity log. There are many other places as well. These are only two examples. If these symbol settings are not found, the result was not being cached, and there would be an inefficient look up every time the symbol settings are needed. This would cause Sierra Chart to use higher than normal CPU usage whenever something like the order list is updated. Normally users would not encounter a problem because only symbols that are known to the current service would be used. But if there was an unrecognized symbol the lookup is not as efficient. This may not really have been much of a problem if at all, but the caching which is now done, does help improve performance. - Apparently on Windows 10, or may be due to some security software users are running, there is a serious memory leak issue when a DLL is unloaded and loaded. The memory is not getting released by the operating system. This is not a Sierra Chart issue but clearly a Windows issue. This causes over time huge memory usage. We have implemented a solution to this as well. This is something that usually only a study DLL developer would encounter a problem with. An average user would not. 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-11-05 09:03:49
|
To post a message in this thread, you need to log in with your Sierra Chart account: