Support Board
Support Board
Search Board
Control Panel
View My Posts / Threads
Direct MessagesDate/Time: Mon, 29 Apr 2024 12:23:20 +0000
Post From: Memory
| [2013-03-21 22:22:47] |
| |
|
This memory usage is not from Sierra Chart. It is from the T4 API. Which we are going to be removing and using a FIX connection. This will dramatically lower memory use. The T4 API uses excessive amounts of memory and CPU usage. We have always known that. Also, we really see no practical reason to support 64-bit addressing because most of the processing goes on within the primary thread for charting and if you really have a lot of charts that require a very large amount of memory. You should distribute the load by running multiple copies of Sierra Chart. Please see: http://www.sierrachart.com/index.php?l=doc/MultipleServices.html Help topic 76 has been updated explaining these additional issues with client-side proprietary API components: Http://www.sierrachart.com/index.php?l=doc/helpdetails76.html Your recent postings have pointed out all of the problems with client-side API components. It's a good example of how code we did not create, provides a very poor impression. 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: 2013-03-21 22:24:11
|