Support Board
Date/Time: Tue, 26 Nov 2024 22:28:54 +0000
[User Discussion] - Interval Update to match Infinity Futures DOM - Needs to be Faster
View Count: 775
[2023-06-05 14:21:07] |
User257205 - Posts: 5 |
Hello, My dad currently uses Infinity Futures' DOM to execute trades. In an effort to get him to switch over to Sierra Charts' Trade DOM / Chart DOM, we were comparing how quickly Sierra Charts' DOM was in updating the current price interval on each DOM and noticed a significant delay in Sierra's DOM relative to Infinity Futures' DOM. I have updated the Chart Update Interval in Milliseconds to the lowest setting possible "10" to ensure I am getting the fastest update to price. Infinity Futures still remains much quicker. In an effort to experiment with speed, I even limited the # of charts to 1 for an instance to test out if that would improve the speed with no success. Is there a way to update the interval speed lower than 10 milliseconds? Or another setting that could make Sierra Charts' DOM to be on par with Infinity Futures' DOM from an update tick speed perspective? Thank you, Jake |
[2023-06-05 15:52:57] |
User753428 - Posts: 163 |
are you using denali? my experience has been that the denali feed, even at its lowest chart update interval speed, still updates slower than the cqg or rithmic feeds. it just isn't as snappy. a while back, many ppl were complaining about this and sierrachart tried to implement solutions such as standard/high compression but such solutions only made a difference if the difference in feed update speed was due to your internet connection in the first place. not to mention, a slow internet connection would usually result in intermittent freezes, not slower updates, so it didn't really solve the originally requested issue in the first place. to this day, i don't think sierrachart quite understands the nature of the problem because everytime someone brings this up, they just review their denali market data server logs and point to some millisecond figure as proof that there is minimum latency and is faster than all other feeds so there is no problem on their end. perhaps on the server end, there is no deficiency but most sierrachart users are retail who trade visually via the DOM or chart. and what many of us can unequivocally say, is that the speed at which the price on the chart updates as perceived by our naked eyes, definitely feels less snappy than other feeds like cqg and rithmic. if your trading requires you to have the snappiest feed, you need to go cqg or rithmic. i've tested this many times and even cqg/rithmic set to 50ms feels faster than denali at 20ms. enjoy it while you can because it's probably a matter of time before sierrachart discontinues support for cqg and rithmic data feeds. that being said, i feel like this issue is only relevant if you scalp. for longer timeframe traders, denali is o-kay. |
[2023-06-05 16:40:52] |
User257205 - Posts: 5 |
Thank you for the insight and thorough response. Yes, I am using denali, which felt like the source of the issue, but didn't want to assume without a second opinion. I was hopeful that it was just a setting change, but yes definitely can't deny cqg/rithmic is the way to go to get the quickest feed for scalping strategies. Cheers, |
[2023-10-26 09:19:59] |
User807055 - Posts: 2 |
Maybe it is something regarding the update interval: I saw this also in TradingView. TradingView only receives data from the dataprovider when there is a trade. So you only get an update of the candle when a trade is done. You will not see any Tick data that is responsible for the trade. So i think Denali and TradingView could be similar and only update the candles when a trade is done in the background. There is maybe no real tick-data-feed. But it is just a feeling. Bookmap is so fast, never saw this speed in Denali Service... |
[2023-10-26 11:41:54] |
Rui S - Posts: 190 |
So i think Denali and TradingView could be similar and only update the candles when a trade is done in the background. There is maybe no real tick-data-feed.
This is not true at all. Denali is a tick by tick data feed and works as such. |
[2023-10-26 13:17:28] |
User852559 - Posts: 40 |
Try lowering the remote buffer delay send time under global settings > sierra chart server settings to 10ms and then disconnect/reconnect and see if that helps.
|
[2023-10-26 15:00:22] |
Rui S - Posts: 190 |
Try lowering the remote buffer delay send time under global settings > sierra chart server settings to 10ms and then disconnect/reconnect and see if that helps.
That's correct but you also must take under consideration that with those settings you will need a computer and an internet connection that can keep up to it, otherwise you will get the very opposite of what you want. Date Time Of Last Edit: 2023-10-26 15:01:53
|
To post a message in this thread, you need to log in with your Sierra Chart account: