"...IB / TWS is not really up to professional standards when considering it as real time data source. Its backfill is very limited (1 symbol at a time) and VERY VERY slow. IB throttles backfills and you can not send more than 60 requests within 5 minutes (it equals to one month of 1-minute data for 12 symbols only).
AmiBroker can not really show its full potential using IB/TWS because of IB limitations. We strongly recommend using TRUE real time data providers such as IQFeed or eSignal. Backfills using IQFeed or eSignal are upto 100 times faster !"
...."+ Implemented workaround to IB weird way of sending tickSize events
Problem was that IB sometimes repeats many times the same tick and sometimes skips some ticks and cumulate them into one tickSize LAST_SIZE event. This is because IB feed was NOT designed as tick-by-tick and never intended to create time&sales series, but rather solely to update TWS display grid. Now the plugin tries to workaround this weirdness by ignoring duplicate tickSize LAST_SIZE events (with the same size) and correcting missing ticks usign CUMULATIVE volume sent with tickSize VOLUME event. Correction is needed because without it we would end up having incorrect total volume (sometimes real trades may have same events so multiple REAL ticks may have same price/size, unfortunately there is no way to detect whenever it is real trade or duplicate generated by IB, so correction according to cumulative volume is the only way to go)."
http://www.amibroker.com/ib.html
AmiBroker can not really show its full potential using IB/TWS because of IB limitations. We strongly recommend using TRUE real time data providers such as IQFeed or eSignal. Backfills using IQFeed or eSignal are upto 100 times faster !"
...."+ Implemented workaround to IB weird way of sending tickSize events
Problem was that IB sometimes repeats many times the same tick and sometimes skips some ticks and cumulate them into one tickSize LAST_SIZE event. This is because IB feed was NOT designed as tick-by-tick and never intended to create time&sales series, but rather solely to update TWS display grid. Now the plugin tries to workaround this weirdness by ignoring duplicate tickSize LAST_SIZE events (with the same size) and correcting missing ticks usign CUMULATIVE volume sent with tickSize VOLUME event. Correction is needed because without it we would end up having incorrect total volume (sometimes real trades may have same events so multiple REAL ticks may have same price/size, unfortunately there is no way to detect whenever it is real trade or duplicate generated by IB, so correction according to cumulative volume is the only way to go)."
http://www.amibroker.com/ib.html