Support Board
Date/Time: Sun, 24 Nov 2024 17:32:51 +0000
Post From: Charts updating slow on live data, blasting fast on replay (Denali)
| [2020-10-01 12:31:38] |
| |
|
We would not recommend going less than 50 ms and the minimum allowed is 20 ms. For remote connections, outside of the local network, typically the average has been about 50 ms. It becomes larger with degraded connections. Adjusting the buffer interval, will only be possible, when using data feed compression. Understand that lossless data transfer is a two-way communication path and it becomes very inefficient with small and excessive packet transfer. From Wikipedia article linked above: Since there is a certain amount of overhead associated with processing each packet, the increased number of packets means increased overhead to process a decreasing amount of data. The end result is thrashing.
The concern is not the server load, the compression time is not a problem for our servers. The concern, is excessive packet flow on the network and side effects of that. 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: 2020-10-01 12:34:30
|