Support Board
Date/Time: Wed, 27 Nov 2024 10:25:55 +0000
Post From: Denali feed slow during news
| [2023-09-01 17:59:19] |
| User753428 - Posts: 163 |
|
for what it's worth, i had chart update interval set to 20ms and i did not experience any freezing today, unlike the other two days. Reading this and other responses, you guys are reporting "subjective" perception on lags which is not very helpful.
if you were following this thread, you would know that one of the two incidences (last Friday) was around a 40s-60s data freeze. that's way too long for it to be a "subjective" perception. Engineering needs the heart beat messages to troubleshoot this further so better to wait for the next news release and follow the instructions provided.
during the 40s-60s freeze, the message log did not print anything. trust me, i was intensely checking the heartbeat messages during that exact moment and it totally skipped over. see my comment on this thread (Glitch in feed at 10am Est). it is post #6. And just to say it respectfully, anyone trading news release on CME from outside the USA should absolutely invest in a dedicated or bare metals VPS server hosted in Chicago.
respectfully, i don't think you understand the problem. ppl aren't complaining about not receiving the data at the "correct time." if there's a news release at 8:30:00am EST, nobody's gonna complain about receiving the tick data at 8:30:50am EST due to latency if they're located in Tokyo. the problem is the manner in which the data is being transmitted and displayed through the front-end sc program. if i'm located in europe or new zealand, there will be a ton of latency so the ticks may come through later than when it actually occurred. but as long as the ticks are displayed in the correctly-timed sequence as it occurred at the exchange-level (albeit with slight latency), ppl would be satisfied. 99% of us aren't running front-running algos that are latency-sensitive. Date Time Of Last Edit: 2023-09-01 18:00:45
|