Re: What is the exact limit on number of requests?
|
Hi Andy. I also introduce 10ms of delay across orders. So far, working well for years. For other requests with `reqId`, I don't apply delay but I have a pacer that will introduce 1000ms delay every 45 requests. For my needs that's enough.
Hope it helps, Daniel.
There are a couple of pages mentioning limits on historical requests and orders.?
?
The last link mentions that I should be able to place up to 50 requests per seconds.?
Meanwhile, when trying to sell iron condor using 4 independent orders, only some of them are being submitted and if I try to wait until all of them are placed, my script hangs.?
Then, I tried to add some delay between placing orders, and now all of them are placed as expected.?
?
for (var i = 0; i < orders.Count; i++)
{
? client.ClientSocket.placeOrder(...)
? await Task.Delay(15)?
}?
?
It seems that a delay of 15 milliseconds is enough.
Anything less than that gets stuck on the way to TWS.?
The same limitations seems to apply to "reqMktData" and "reqContractDetails" calls.?
?
Question?
?
How reliable is this hardcoded delay of 15 ms.?
Is there a recommended delay between requests anywhere in the docs??
|
Join twsapi@groups.io to automatically receive all group messages.
