Welcome to NexusFi: the best trading community on the planet, with over 150,000 members Sign Up Now for Free
Genuine reviews from real traders, not fake reviews from stealth vendors
Quality education from leading professional traders
We are a friendly, helpful, and positive community
We do not tolerate rude behavior, trolling, or vendors advertising in posts
We are here to help, just let us know what you need
You'll need to register in order to view the content of the threads and start contributing to our community. It's free for basic access, or support us by becoming an Elite Member -- see if you qualify for a discount below.
-- Big Mike, Site Administrator
(If you already have an account, login at the top of the page)
Thanks, I don't use the IB data feed but use Kinetick, which seems OK, though occasionally I notice that a few ticks "bunch up" and get delivered in a burst which causes the strategy problems.
I think that is caused by Internet connectivity latencies, which I hope would not happen with the server connected via a big pipe in a datacentre.
Can you help answer these questions from other members on NexusFi?
Many thanks for that Crow. I have a strong PHP/MySQL background so it shouldn't be diffcult to pick up Java, if need be. It was straightforward moving to C#.
So far, the only automated strategy that I've found to be reliable uses small profit and stop loss targets for quick scalps where you can have as much control as possible (which still isn't much), however this is causing the problems discussed in this thread.
My mate is a Java wizard and definitely uses it on Linux, so I don't know how he gets around the problems that you mention. He uses large databases for storing historical SR levels, I believe, so he has to handle database interaction under HFT conditions too.
I wish I could talk to him about his systems in more detail, but he works for a large fund and their systems are their business and are therefore highly confidential.
I've been investigating further into what is causing the rejected order situation.
It doesn't seem to be the MTF computations, but the fact that the strat is placing a stoplimit order two ticks above the trigger bar. As I am using COBC= true, by the time the trade entry order is placed, the market has moved past it.
Whilst I'm relieved that mtf doesn't seem to be causing problems, at least yet, it does mean that I'm going to have to revisit the trade entry criteria to place the entry further from the immediate price action when trading CL.