Is it possible to ping your WoW server from (say) the Windows command line? That would give you an idea of how low the latency could be.
Is it possible to ping your WoW server from (say) the Windows command line? That would give you an idea of how low the latency could be.
How would I do that?Quote:
Originally Posted by 'Freddie',index.php?page=Thread&postID=160035#post 160035
Anyway I think that Vista has the TCPNoDelay feature off by default. I don't think it's kept in the registry, either.
I found these settings and all of them were off.
- Open Control Panel.
- Click Programs, and then, under Programs and Features, click Turn Windows features on or off.
-or-
Click Classic View, double-click Programs and Features, and then in the tasks pane, click Turn Windows features on or off.- Expand Microsoft Message Queue (MSMQ) Server, expand Microsoft Message Queue (MSMQ) Server Core, and then select the check boxes for the Message Queuing features that you want to install.
- Click OK.
- If you are prompted to restart the computer, click OK to complete the installation.
To ping a server, you open a commmand prompt box and type "ping" followed by the IP address of the server. But there are lots of forum posts that say Blizzard's servers do not return ping requests so this probably won't work.Quote:
Originally Posted by 'TheBigBB',index.php?page=Thread&postID=160036#pos t160036
If MSMQ is off, then presumably TCPNoDelay has no effect. But the absence of a registry setting for TCPNoDelay may not mean anything because -- well, check out the last line on this page where Microsoft documents TCPNoDelay:Quote:
Anyway I think that Vista has the TCPNoDelay feature off by default. I don't think it's kept in the registry, either.
http://technet.microsoft.com/en-us/l.../cc783904.aspx
It says, "This entry does not exist in the registry by default. You can add it by using the registry editor Regedit.exe." That means that even when MSMQ is on, Windows doesn't put that item in the registry. You have to enter it yourself.
All of this is pretty interesting because the web is full of posts and articles advising people that TCPNoDelay is a global setting for Nagle. Apparently they are wrong. It also looks like Microsoft hasn't provided any way to turn Nagle off globally.
If those things are true, there's an opportunity for some clever programmer to write an app that sets TCP_NODELAY on sockets that belong to other programs.