I was wondering if any oceanic players have had a chance to download the 2.3.2 latest ptr version and see if there is any difference with the Nagle's Algorithm supposedly disabled?
I'll be downloading it sometime soon when i'm not internet capped, however I was reading a different forum and read this;
I've just been on the PTR with the build that has turned off the Nagle algorithm.
I noticed that yes, my reported latency was less than on live (started off around 180 but settled in around 380). Quartz was reporting most casts in the 500 range.
It doesn't sound too promising by that, and I think there is still a way for it to be a need for things like lowerping (which I am using) to give the game its maximum performance, especially in PvP when the lower your latency is, the better you are.
I was wondering if any oceanic players have had a chance to download the 2.3.2 latest ptr version and see if there is any difference with the Nagle's Algorithm supposedly disabled?
I'll be downloading it sometime soon when i'm not internet capped, however I was reading a different forum and read this;
It doesn't sound too promising by that, and I think there is still a way for it to be a need for things like lowerping (which I am using) to give the game its maximum performance, especially in PvP when the lower your latency is, the better you are.
Lowerping indirectly does what disabling Nagle's does.
Anyway, I personally didn't see any substantial results with lowerping or Internode's solution, but a friend of mine in the same city did. I haven't tried the new PTR yet, I hope it's better.
I understand tunneling over SSH, but don't have any experience setting up a server. What, if anything, do you need to do on this server before you can route WoW traffic through SSH to it?
Short answer: Nothing.
Long answer: sshd needs to be configured to allow tunnels, and your firewall needs to not be so locked down that it won't allow the traffic. However, most servers should be configured this way "out of the box". If you try it and it doesn't work, the error message should be enough to clue you in as to where the problem lies.
The Lowerping and the internode solution has had some success in our guild and for some other people that i do know, but some had issues with latency spiking, also sometimes there latency gets so high they switch back.
If we are patient in a year or two or three australia's tele-communications companies will start the migration to MPLS which will improve out bandwidth overseas and we should see improvements with gaming online and overseas, including wow.
Regardless my ping is between 250 to 280 stable after i did some network card tweaking, XP tweaking and also disabling the use of Nagals algorithm on certian ports that wow does use. I used to have 400-500 latency before i made my changes, but i can sure say it has improved my ability to react and be alot more effective
I can't stand not playing via ssh now the difference between 350-500ms and 200-250ms is huge, if I have a ping of 500ms I just log off and go out and watch a movie or something.
Oh I also tested cadaful's java proxy and it doesn't seem to have any affect on my ping, at least not as much of an effect as using ssh does.
The universe is run by the complex interweaving of three elements. Energy, matter, and enlightened self-interest.
I wonder, how did you disable the Nagle algorithm for only ports that WoW uses?
Afaik the Windows registry changes affect your whole connection?
Using a Linux box allows you to do this, either a real linux box or a virtual box. (Both of those are links, on my machine there is not much of a colour difference between a link and non-link.)
I am currently using the registry change and while my in game latency has gone down by about 100ms, i dont really seem to feel any less laggy using instants and whatnot. Would it be worth my time investigating lowerping or a ssh thing - or are they pretty much the same as using the registry tweak?
I used a VMWare client running Debian Linux as a proxy with the WoW ports forwarded from my main PC to the Laptop running the client. Have a troll on the WoW Jubei' Thos forum for some walkthroughs.
Cut my ping by an average 100-150.
Also, I saw a mention earlier of Jubei being on Bloodlust BG.....it's on Vengeance.
The lowerping service provides a lot better latency that disabling the Nagle algorithm. I use LP and get a consitent 170ms ping playing from country NSW. I get a 450-500ms ping while not on the service. The difference I can see in game is amazing, its a completly different game at a lower ping. Instants feel instant, I can react to things quicker (being able to see them happen, as well as the time it takes my spells to go through). Healing raid frames are a lot more responsive as I can see things like incoming heals a lot better and heal accordingly.
From my experience using a decent ssh proxy seems to be significantly more responsive + less spiky than the registry tweak or a local proxy linux/java.
The universe is run by the complex interweaving of three elements. Energy, matter, and enlightened self-interest.
I just signed up to the forums tell you guys my results -
First off I decided to wait for the official patch before I fooled around with the settings listed (just wanted to be sure and I didnt find out about this till a couple weeks ago).
So the patch hit ... and it did nothing for my pings. I'm playing from the UK to a US server(old friends there) recently got a job in the UK. And my pings usually hover between 250-400.
While not terrible - my plan was to do arena and pvp mainly and I want the best ping possible.
After the patch 2.3.2 My ping was 260-440 So basically not changed ... I tried rebooting.
...
So I tried the first suggestion of adding a "TcpAckFrequency" to my registry.
Results after I rebooted - hovering between 160-200 crossing my fingers here and hoping it stays below 200.
also wondering if I should do the second part I have seen about the "TCPNoDelay"
2.3.2 with no registry changes, in game latency = 290 ms
2.3.2 using a linux box running socat, in game latency = 175 ms
So it would appear Blizzards solution is ineffective. It would be interesting to check if TCP No Delay is in fact set in the communications between the wow client and server.
Personally, I loaded the patch, loaded into the game (in Hinterlands, so relatively quiet) and latency was around the 170ms mark (this is with the registry tweaks still applied).
I then reverted the registry tweaks, rebooted and loaded back into WoW and latency was around the 320ms range.
Next I re-entered the tcpackfrequency registry change, rebooted and loaded WoW, and was back to the 170ms range ping. The tcpnodelay appears to be superfluous.
Network performance and connection being one thing, wow itself takes up most if not all of the CPU time if it's able.
Taskmanager shows wow continuosly at 97-99% on my computer.
This causes any applications in the background to be completely choked, downloads to barely work, torrents to fail, and tabbing to look at any forums nearly impossible.
As a small fix i found that going into the taskmanager and setting wow's priority to "below normal" instead of "normal", that all processes suddenly had a lot more breathing space.
I can tab to IE7 or Firefox and browse without any trouble, torrents work fine, winamp doesn't struggle as much either.
The only downside is that wow sometimes gives a stutter if you're doing anything really big.
I'd test this little trick for network latency, but mine seems quite fine one way or the other.
Perhaps somebody with high latency issues could give it a try?
Also, does anyone have an idea how to start wow.exe in "below normal" mode by default or at least automatically?
It does get somewhat of a chore to have to set the priority each time you relauch wow.
-= Random Ravings - RSS Feed =- Rogue and Hunter stuff here. As well as guides to get you trough your spare time.
Also, does anyone have an idea how to start wow.exe in "below normal" mode by default or at least automatically?
It does get somewhat of a chore to have to set the priority each time you relauch wow.
Make a text file on your desktop and put the following text into it
@echo off
START "" /BELOWNORMAL /B "C:\Program Files\World Of Warcraft\wow.exe"
Rename it as a .bat file instead of .txt and it should work fine. If it doesn't work you might need to remove the leading "" but you need that for it to work on systems with no console access.
Any parameters for WoW like /opengl can just go after wow.exe"
Network performance and connection being one thing, wow itself takes up most if not all of the CPU time if it's able.
Taskmanager shows wow continuosly at 97-99% on my computer.
This causes any applications in the background to be completely choked, downloads to barely work, torrents to fail, and tabbing to look at any forums nearly impossible.
As a small fix i found that going into the taskmanager and setting wow's priority to "below normal" instead of "normal", that all processes suddenly had a lot more breathing space.
I can tab to IE7 or Firefox and browse without any trouble, torrents work fine, winamp doesn't struggle as much either.
The only downside is that wow sometimes gives a stutter if you're doing anything really big.
I'd test this little trick for network latency, but mine seems quite fine one way or the other.
Perhaps somebody with high latency issues could give it a try?
Also, does anyone have an idea how to start wow.exe in "below normal" mode by default or at least automatically?
It does get somewhat of a chore to have to set the priority each time you relauch wow.
Try to run WoW in Windowed fullscreen mode, I find it slightly better than the normal mode. I find it take up less resources this way too for my computer.
Also what's your computer specs? Normally resource problems could be as easy as spending 20 bucks and add/replacing your ram stick
I have problems with this bit, in my regedit i have 14 NIC interfaces listed, 3 of which contains my IP (on my local network, none contains my internet IP). Which one could it be?
None of them stands out either, they have 16, 26 and 28 settings respectivly.
This sounds similar to mine. Question is, should I modify all or how do I identify the appropriate NIC interface ? I live in the UK if that has any relevance.
Also,I have my ISP connection set up on one (older) PC running Windows XP and have the connection to my WoW PC by cable from the router. Do I need to modify the interface TcpAckFrequency on both machines or just the WoW machine ?
A big advantage of the java proxy variant is, it works as well on a Mac, not just on Windows.
Since the proxy is only part of the solution, you need a Socks redirector. On Windows FreeCap is one, on Mac, this tsocks version 1.8.3 for Mac OS X 10.5 Leopard should work (can't test it myself).
I know this is a couple months back in the thread, but the information I've found reading the posts from December has been rather helpful to me. I play WoW from my laptop, and it's sometimes attached to networks that don't like to let it pass its information through. I also have a linux box at my own home that I can SSH to and do port-forwarding with.
I tested running WoW with a SOCKS redirector once, and it worked - i was able to connect just fine and latency almost as good as I would have from my home computers. But, is redirecting WoW's communication through a SOCKS layer actally legal? I'd rather not get banned over something like this if Blizzard decides SOCKS proxying is against the TOS.
I think i mentioned this before in this thread. I have been running a socks proxy for wow for about a year while living in a university dorm without negative effect on my account.
It's not illegal and Blizzard doesn't care about that.
What you must not do is interfere or intercept with the datastream passing through. You see, for example the written chat is there in the data stream in plain text. No matter which faction talks. So you can actually grab everything said in your vincinity and understand it, even if it is said by a member of the opposing faction. The translation to "gibberish" for the other faction happens in your client. You could therefor do something to extract this information and make this available to you. That is not allowed. While this example is rather simple, there are other such things having much more severe consequences you could do when you manipulate the data stream.
Also, when you set up a public proxy for many people, then for Blizzard's automated systems it may look as if everyone using that proxy (and coming suddenly from that IP address) is using a powerlevelling service or some such. That may or may not trigger an automated alarming system. If you are the only one using that proxy, then that is however no issue at all.
That all said, since the patch went live my normal latency ingame is indeed about 40ms lower. I now average at around 40ms from 70-80 before. For me there wasn't any need to optimize using a proxy as I was already low-latency but now I am at that spot without any proxy or registry manipulation. It took a few days after the patch though to stabilize at this point.
Yeah, I'm the only one on the proxy. It's just an old hulk of an IBM I had laying around and installed linux on. Thank you koaschten and Cadfael for clarifying.
Some other people had this as well, I am not sure as to why this entry is missing.
You can add it yourself by copying the text below, saving it to a text file and rename it msmq.reg. Then right-click the file, select merge and click ok to the box that pops up. This registry file has the TCPNoDelay setting already entered.
12/21/07, 3:40 AM
Similar Threads
