NT7b5: IB connection adapter historical request limitations

[tickling]

When trying to load historical data via IB, NT hits IB's API pacing limits for almost every non trivial request, making it very hard to use.

Subjectively speaking, this seem to happen more in NT7 then NT6.5.

I was wondering if the IB adapter could abide by IB API pacing rules and avoid this. The rules are well documented and should not be problematic to implement. Thanks for considering this.

[NinjaTrader_JoshP]

tickling,

Nothing has changed in terms of how data is downloaded from 6.5 to 7. If you are using the same account on 6.5 and 7 remember that effectively doubles your requests and it could just be hitting the limit when you are in 7.

[tickling]

Thanks for your answer
I am only having one NT instance at a time, not two.
Yes this problem also exists in 6.5. I wanted to suggest that the IB adapter could impelement the IB TWS API pacing rules for historical data so people using Ninja and IB could load a workspace with several charts without running into trouble and incomplete charts. The pacing rules are documented in IB's API and if implemented, could make IB usage via Ninja much better.

[NinjaTrader_JoshP]

Thank you for the suggestion.

[Harry]

Loading data from IB

Hello Josh,

I think there is a significant change between NT 6.5 and NT 7 here. This applies to the case, when IB cannot (congestion) or does not allow to (pacing limits) further load any data. Whether this is the case, can be checked in real time directly within TWS, as TWS charts will not load either.

NT 6.5. : A loading popup shows up. If nothing happens the "Abort" button can be selected, and the chart will be redisplayed without further data being loaded.

NT 7: The loading information is shown in the upper left corner of the chart. I did not find any way to abort the loading process. So the chart remains empty, and nothing can be displayed, while being connected to TWS. To display the data, you have to disconnect, close the chart and open a new one.....

Please give me back the "Abort" button. Can't use IB data without it!

[NinjaTrader_JoshP]

Harry,

Abort button is in the Control Center status bar on lower right.

[Harry]

Sorry Josh,

using this for years, but do not know what is a control center status bar and where to find it!

[Harry]

Found it now, only shows the abort button, when loading a larger chunk of data. Will test it tomorrow, but if it is there, that should do the job. Maybe you could color it, when it pops up, to make it easier for users to find it....

[NinjaTrader_JoshP]

Harry,

This is a new feature in 7 to replace the popup message for loading data and other things. Lower right corner where it use to say ATI is where the status bar is for the Control Center.

[Aussie2]

IBs pacing parameters

Apparently IBs pacing parameters are 60 queries per 600 seconds or 10 minutes, and also requests must be spaced by a minimum of 1 second apart.

So how about introducing these to NT7B?

[tickling]

Just for the reference, here is a quote of the exact limitations IB expects from data requests:


All of the API technologies support historical data requests. However, requesting the same
historical data in a short period of time can cause extra load on the backend and subsequently
cause pacing violations. The error code and message that indicates a pacing violation is:
162 - Historical Market Data Service error message: Historical data request pacing violation
The following conditions can cause a pacing violation:
• Making identical historical data requests within 15 seconds;
• Making six or more historical data requests for the same Contract, Exchange and Tick
Type within two seconds.
Also, observe the following limitation when requesting historical data:
• Do not make more than 60 historical data requests in any ten-minute period.


Again I believe if those are implemented in NT7 connection adapter it will be very significant for those of us who rely on it.