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)
You are probably aware of this, but I read somewhere where NT/Zenfire does not hold all order types at the exchange. Instead some are held on NT and only sent to the exchange when price triggers on NT. So in these cases round trip latency could have an effect, especially if you are trading something fast like CL.
I think normal limit orders are held at the exchange/Zenfire, but if you are using ATM with say a OCO profit target and stop loss target, then I think these maybe held in NT on your computer.
I am sure I read this on futures.io (formerly BMT) somewhere.
Oh and PS: good to see the Kiwis can beat the Aussies at something - 224ms vs 260ms latency
Can you help answer these questions from other members on NexusFi?
Now Steve we will keep the Nation rivalry out of it. I mean really you are a State of Australia anyway. lol
Interesting thoughts though on the handling of orders. It may be the case.
Was in NZ last year and had a great time. Sth Island is majestic.
Take care
Agree with you 100 %
I've heard that some tweaks can be done in Windows register which can make ping speed about 30 % faster.
Keeping in mind your IT background do you know that by chance or can investigate ?
I'm afraid that's a myth.
There is nothing you can tune that will make ping times better.
TCP/IP is a connection oriented protocol. A client and server will send a burst of data and then wait for the other side to confirm receipt.
This 'burst' is called a 'window' in TCP terms, and will typically vary from 17-64KBytes.
This can be a problem on high latency connection as you can end up spending a long time waiting for that receipt before sending more data.
This problem gets worse the faster the connection.
The tools you're thinking about tune how much data is sent in each window, so they may help with downloads, and perhaps when delivering historical data when you open a new chart.
But nothing can reduce the latency, other than a straighter/shorter path.
Pure physics..
Zoltran,
Thank you.
Do you know and can suggest/advise any reliable tool I'm looking for ?
Also can give your opinion about below In
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces
create
DWORD with value 1 and text "TcpAckFrequency"
In HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSMQ\Parameters
create
DWORD with value 1 and text "TCPNoDelay"
Tuning parms like this will only affect longer flows that transfer a lot of data, as they effectively increase the amount of data sent before the sender pauses and waits for an ack. But ..in this case, only you are setting them.. and ideally you want to see it on the server too.
Tuning cannot help latency sensitive applications...
Thank you.
Just for good orders sake...I'm not arguing with you, I'm discussing, asking for advice.
I'm heard about such prog as CFOS, but not tried that yet.
Seems that prog can reserve channel for special needs as well as special IPs.
I do not using any voice and video chats, so for example I don't need channel optimized for that. cFos Software GmbH
Can you please advise your opinion about that (Germans usually do good and reliable things)
Also question about CPU, how I can test and in case needed fine tune that ?
All runs fast, but seems I got some "bug" there ?
Andrew, no matter how well tuned is your TCP stack on your PC, 95% of the latency is not under your control: the dozens of routers/links between you and the destination host.
For some specific pro trading applications and bots, some specific hardware and fine TCP/UDP tuning is done (or specific hardware/drivers are designed), and it's useful in HFT, but the guys have some direct links to the exchanges, which is not the case here...
If all respect to you I see 2 reply from you which tell "stop do that and that".
Thank you for warning, but I'm looking for info not warnings.
+ your last reply regarding institutional softwares, datafeeds was great insight, but no any reply to questions posted on that.
I do not intend to offend you, I treat info from you very useful, but I need info, not warnings.
That is very interesting also
QUOTE
For some specific pro trading applications and bots, some specific hardware and fine TCP/UDP tuning is done (or specific hardware/drivers are designed)
UNQUOTE
Can you please provide more specific info apart common phrases.
Repeat, I do not offend you, I just want to say I need info, warnings I know on my own perfectly.
P.s. Sam are you "connected" ? I do not remember seems in Paris exists (apart from 4 other EU cities) direct transatlantic cable to US exchanges