Let me try to put an end to the IB streaming/snapshot debate. There are enough wrong comments on both sides of the argument.
1) IB Datafeed is STREAMING. It just isn't tick-by-tick. Its MAX update rate per symbol is 0.7 or 0.5 or whatever. There is a big difference between that and snapshot quotes, so please limit your comments to something you really know about.
2) As for tick charts being built from a NON tick-by-tick datafeed, it seems to defeat the purpose if you are watching a high volume security. Think about it - The whole point of tick charts is that each bar represents X number of trades instead of time. If you are watching a 50 TICK chart on a security that frequently has more than 2 trades per second, then the limit of 0.7 seconds on the update in affect makes that tick chart the same as a regular candlestick chart with a frequency of 35 seconds - its no longer a tick chart. (you get a 1 tick per 0.7 seconds. 0.7x50=35)
3) The comment about 30% of the ticks being good enough statistically is valid for regular candlestick or OHLC charts. It is NOT valid for TICK charts since the update limitation screws up the very thing that the tick chart is used for - to reflect the pace of trading. If it was a steady 30%, that may still be OK. However its not. If a security trades 10 times per second or 5 times per second, it will get the same number of updates through IB datafeed.
4) With IB, there is another issue - what is a tick? Their datafeed sends streaming fields, not full records. You may get 1 update on LAST price, another on VOLUME and yet another on BID. Each one is a separate item. The order is not guaranteed. Identifying which updates go together and thus constitute a field is possible, but definitely not an exact science. This has less disruptive affect on tick charts than the update limitations
The above applies to all Applications that use IB or another non-tick-by-tick datafeed as a source
Jerry Medved
http://www.quotetracker.com