You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
Good broker for automated futures and options trading?
- Thread starter snackly
- Start date
RedRat,
TT does not aggregate last traded quantity by default.
There is a gateway setting in the Aconfig that may be set to aggregate last traded quantity. This is off by default but in your case, it sounds as if the flag has been set to on so the last traded quantity is aggregated.
Please contact your FCM / TAM to look further into this.
Regards,
TT
TT does not aggregate last traded quantity by default.
There is a gateway setting in the Aconfig that may be set to aggregate last traded quantity. This is off by default but in your case, it sounds as if the flag has been set to on so the last traded quantity is aggregated.
Please contact your FCM / TAM to look further into this.
Regards,
TT
Quote from x_diver:
Did this data come from X_TRADER or the TT FIX Adapter?
My data came from TT FIX Adapter.
Quote from TT Guru:
TT does not aggregate last traded quantity by default.
Thank you for support. I am personally satisfied with incoming data. Right now I do not need tick quality. In the future I will contact my broker.
Quote from taotree:
I was on the phone with a guy from AdvantageFutures yesterday and it sounds like for the NinjaTrader feed at least, TT aggregates messages--they coallesce trades to a single message per 100 milliseconds. But, he said T&S information inside that should not be aggregated.
He said that he could get me an unfiltered feed but that generally during fast market moves, that results in a frozen DOM and so they don't do that usually.
So if you need to set TT to coalesce market data (bid/ask) at 100 millisecond intervals in order for Ninja to work properly, then I'm assuming that Zenfire is also coalesced for Ninja?
Quote from x_diver:
So if you need to set TT to coalesce market data (bid/ask) at 100 millisecond intervals in order for Ninja to work properly, then I'm assuming that Zenfire is also coalesced for Ninja?
the market data for ninja through Zen-Fire is NOT coalesced (filtered, aggregated, ...).
Quote from x_diver:
So then if Ninja can handle the full feed from Zenfire, why can't Ninja handle the full feed from TT? This is very strange. Can someone please explain this?
I can't promise this is why, but there is at least one significant difference:
Zenfire is binary data. TT is FIX. FIX is a text based protocol with tags and so it takes a great deal more processing to parse and handle it. It is likely it takes significantly more bandwidth, too--though that depends on if it uses fastfix or not (I'm not sure if it does--I haven't seen anything that says it is, so I assume not).
But that SHOULD not make a difference, unless somoene runs a strategy on hundreds of stocks. Parsing 1000 lines of text per second should not really stress a modern cpu.
I am doing conversions of historical data at the moment, and I run through 20.000 files of daily closes in just a minute or two, incoluding all file overhead (open, close). That is a lot more tick per second than the fix stream does.
Must be imho some programming glitch in the connecting code.
I am doing conversions of historical data at the moment, and I run through 20.000 files of daily closes in just a minute or two, incoluding all file overhead (open, close). That is a lot more tick per second than the fix stream does.
Must be imho some programming glitch in the connecting code.
Quote from NetTecture:
But that SHOULD not make a difference, unless somoene runs a strategy on hundreds of stocks. Parsing 1000 lines of text per second should not really stress a modern cpu.
I am doing conversions of historical data at the moment, and I run through 20.000 files of daily closes in just a minute or two, incoluding all file overhead (open, close). That is a lot more tick per second than the fix stream does.
20,000/minute is only 333 per second.
It's my understanding that ES data at least (which is what I was talking about at the time) can be a LOT more than 1000 ticks per second when news hits or something like that. Keep in mind that it handles market depth as well. Sometimes there can be 1000's of ticks per second. Multiply that by depth of market (5 on each side, so times 10 and also times it changes more than ticks happen) changes and it could be some 10k-100k lines per second.
And some people do run heavy strategies/indicators across multiple instruments and such.