Support Board
Date/Time: Sat, 08 Feb 2025 17:54:46 +0000
Is the DTC Server possibly adding a large latency in the market depth updates
View Count: 591
| [2020-07-20 08:12:35] |
| User442651 - Posts: 25 |
|
As soon as a message is received by the stream I stamp the time with the client's clock. This is compared with the timestamp in the MarketDepthUpdateLevelFloatWithMilliseconds message. I am finding that there is consistently a latency of about 350ms: Message received at 2020-07-20 04:04:46.1515. Type: MarketDepthUpdateLevelFloatWithMilliseconds, Size: 29 Received market data for XBTUSD-BMEXT. Timestamp: 2020-07-20 04:04:45.7880, Client Timestamp: 2020-07-20 04:04:46.1512, Latency: 00:00:00.3632265 Message received at 2020-07-20 04:04:46.1836. Type: MarketDepthUpdateLevelFloatWithMilliseconds, Size: 29 Received market data for XBTUSD-BMEXT. Timestamp: 2020-07-20 04:04:45.8310, Client Timestamp: 2020-07-20 04:04:46.1834, Latency: 00:00:00.3524565 However, the ping round-trip time to bitmex.com is about 95ms. Is is possible that DTC server is creating a lag of about 300ms? |
| [2020-07-20 08:56:51] |
| User442651 - Posts: 25 |
|
Btw, I am certainly hoping this is a problem on my end, or else the DTC Server will not be of use to me. My understanding was the DTC Server actually has sub-millisecond latency. Is this correct? |
| [2020-07-20 10:43:40] |
| |
|
The data is not coming directly from BitMex. So there is going to be an increased latency. But not as much as you are seeing.
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 |
To post a message in this thread, you need to log in with your Sierra Chart account: