ProRealCode - Trading & Coding with ProRealTime™
There is indeed a language “problem”, and it’s hard for me to express myself well in englishFrom your written word, you are expressing yourself extremely well in english … I understood everything you wrote! Had you not mentioned a language problem, I would have thought you were a native english speaker pointofbrew
I have up to 8 systems 1H, 4H that start a trade on Monday morning 09.00 in Dax40. Do not ask about the execution. Only rarely is there a system that starts trading at 09.00.00. 09.00.01-09.00.07 seems to be the norm.(emphasis is mine) Of course we should know about the execution, because it is all about that, right ? So … normal Market orders ? But John, your post makes me think of something very different … This is Eurex, right ? well, Eurex has its own order book and it is not at the broker’s. E.g. Nasdaq, which I showed in this post, has its order book at the broker. Thus, my order is given directly to for example Interactive Brokers. Or, in the case of IG, to IG. Not so with Eurex … If I am talking from my neck, let me know. Somewhere last week I talked about the extra 0,25 I need to pay (to Eurex) when I move a pending order. But, 10 moves are for free per running position. Thus, if my trailing would last as long (xx bars) as I showed in the post above, I am charged xx minus 10 times 0,25. This is because of the extra effort involved around this virtual extra step in the order process. Please note that while I got this data from IBKR (my AutoTrading for DAX and ESTOXX is at PRT-IB), I take it that this counts for IG just the same. It is Eurex which maintains the orderbook(s) and I would not know how IG could go around it. What I am now suddenly thinking is that this just takes round trip time. Maybe more than one communication back and forth. This is about asking, confirming, executing, and all the more stuff I don’t know much about. I wouldn’t know how pointofbrew’s observation wouldn’t be logical. Never mind I don’t understand his means of testing yet. @pointofbrew, did you test this same on Nasdaq ? if not, can you ? And please ignore my well meant advices for now. Just do your thing in the same way. And John, despite that you may see the same thing as pointofbrew does, your 09:00:00 thing is exactly what I was talking about, but inverse : at that time the whole world *is* trading and move markets (make that the whole of Europe). All Eurex stock markets open, and that may cause some delay in all the communications (interfaces) to all directions. I mean, you may see a different result on 11:00, or even better 11:07:24 (etc.). You will see the same on 08:00, 10:00, 15:30, 17:30, 22:00, 23:00, because these are all market opening/closing times. I know from PRT-IB what all can go wrong at 22:00, just because the US closes its stock markets (me trading Futures which stay open till 23:00). I even have excluded that moment from trading because IB can’t cope there (for Autotrading and in communication with the outer world (IB)). … But I rather want pointofbrew to be right … and that there *is* this delay.
I mean, you may see a different result on 11:00, or even better 11:07:24 (etc.). You will see the same on 08:00, 10:00, 15:30, 17:30, 22:00, 23:00, because these are all market opening/closing times.I woke thinking the same as above, then read Peter’s post. It be good if pointofbrew could run his code, but with times not on the hour and also avoiding the times Peter states above. Times could be set at exactly 2 minutes past the hour, or 13 minutes past the hour or similar, but no multiples of 5 mins, e.g. not 5, 10, 15, 30, 45 … etc mins past the hour, as these are all often used trading times. If times at exactly x minutes past the hour (excluding above) are used then it be easy to spot delays in the seconds figure.
For me, this is the “normal” operation of the order book…
The order book depends on the supply of the buyers and sellers (liquidity) and sometimes it can take a few seconds for your order to be (completely) filled…
Your coding copilot for ProRealTime™. Ask in plain English — get clean, ready-to-paste indicators, screeners and systems.
Slow order management automated trading 1 second timeframe
This topic contains 25 replies,
has 5 voices, and was last updated by pointofbrew
2 years, 9 months ago.
| Forum: | Platform Support: Charts, Data & Broker Setup |
| Language: | English |
| Started: | 01/18/2024 |
| Status: | Active |
| Attachments: | 8 files |
The information collected on this form is stored in a computer file by ProRealCode to create and access your ProRealCode profile. This data is kept in a secure database for the duration of the member's membership. They will be kept as long as you use our services and will be automatically deleted after 3 years of inactivity. Your personal data is used to create your private profile on ProRealCode. This data is maintained by SAS ProRealCode, 407 rue Freycinet, 59151 Arleux, France. If you subscribe to our newsletters, your email address is provided to our service provider "MailChimp" located in the United States, with whom we have signed a confidentiality agreement. This company is also compliant with the EU/Swiss Privacy Shield, and the GDPR. For any request for correction or deletion concerning your data, you can directly contact the ProRealCode team by email at privacy@prorealcode.com If you would like to lodge a complaint regarding the use of your personal data, you can contact your data protection supervisory authority.