“optimize network for speed”

Understanding what “Optimize network for speed” does.

History:
Originally added when 4.0.6 was launched, this option was designed with intent to reduce latency while in instances by using additional bandwidth and reduced packet sizes, as well as disabling nagling algorithm (selective acks or packet acknowledgements or “naggling”) on application specific level instead of an OS wide hack like the leatrix fix).

This option was later hotfixed to be disabled when blizzard realized this feature was not for everyone.

In 4.1 this feature was brought back with a toggle so that users had the option to turn it off should they have problems with it. However it is ON by default (important to note this).

What it does:
Firstly, this feature does same thing leatrix does. It disables packet piggybacking acks to remove any information delay caused by this delay of information. To understand what this means I will use a metaphor. Imagine two people playing catch with a baseball with a guy in middle announcing throw count every 2-3 throws. The information is obtained, but not in realtime. It’s more efficent as it uses less words, but in terms of real time information, inferior. Now imagine instead that announcer is announcing after every single toss. So you get more real time information on throw count, but at the cost of additional words used. Now just substitute baseballs with packets, and words with network bandwidth.

That is not all “Optimize network for speed does”. Based on data i’ve collected there is a lot more to it then that. So even people who already had nagling disabled in their OS with leatrix, saw additional reduction in latency with new option as well. It seems the option also uses smaller packets. Being smaller, they are transmitted more frequently. So imagine those 2 catchers were replaced their baseballs with golf balls, and started launching them 3 times as fast. Now you have a much higher throw count. But at even more network bandwidth requirement.
This needs citation but nagling alone doesn’t explain things so something else is at work, this is just my theory.

This what optimize network for speed does, it makes wow use SUBSTANTIALLY more bandwidth.

This feature is only used in INSTANCES. It has no baring on behavior outside of battlegrounds/arenas/dungeons. Regular world servers use old network protocols and not this new option.

What is network lag?:

Network lag is response time between your computer, and remote computer. This is NOT fps (frames per second). This has nothing to do with graphics lag. These are two different types of lag.

Network lag can be caused by ISP problems, bad wiring, bad router, any number of bad equipment problems. But it can also be caused by bandwidth saturation. Your connection is at it’s bandwidth limit and unable to keep up with the demand of network information being sent/received. This guide will only focus on the latter, something we can control with the “Optimize network for speed” option.

So is this option right for me?:

If you are lagging only in instances, particularly in combat?
If you answer yes, chances are you need to turn this option off. Based on extensive data I collected first couple weeks of 4.1. In a 25 man raid, just to give you an impression of what exactly that option really does. with it off I use 16kbps upload and about 160kbps download. With it on, I used 320kbps upload and 480kbps download. Download seemed to use about triple bandwidth with option on, but upload seemed to use 20x the bandwidth and it wasn’t even maxed out cause 320kbps IS my upload cap. So naturally with option on I simply could not raid 25 mans on my 1.2M/320kbps DSL connection. However in 5 mans i was fine with about breaking even latency, and in 10 mans was managable with slightly higher latency then i had with it off. My bandwidth wasn’t capped in 5s/10s but it was high enough to negate the usefulness of the option being on as the additional bandwidth saturation canceled out the benefits and raised latency not lowered it. Just didn’t spike it to point of unplayable lag or DCing like 25s did. Based on data I collected and talking with others I have come up with the following table as a minimum bandwidth requirement I’d say this option needs.

5man:
.5M download .5M upload
10man
1M download .6M upload
25man
1.5M download 1M upload

This of course is rough estimates so the true test is your latency, if your latency is higher when it on then with it off, then you don’t meet bandwidth requirements for that encounter to have it on. but on another smaller less detailed fight you may get lower latency with it on.

What if it’s just certain fights?:
Certain fights use substancially more bandwidth then others. One common one brought up a lot is ZG: Venoxis. It may appear the fight itself is bugged since it’s only one that lags you. But you may not have run a 10 or 25 man with enough data yet to compare the results. This fight, although a 5 man, has a lot going on and may be enough to saturate your connection and lag you out with the option turned on. It could also ver well be bugged in a way that makes it use more bandwidth then it probably should. either way, you should turn this option off as at least for me that solved the problem.

What if I’m normally fine but tonight my ISP is sucking?
This option should also serve as a helper for situations that may arise with ISP. Perhaps your ISP is not getting advertised speeds or is bad during peak hours then good in off hours. So you only lag during these peak hours. You should still turn option off. Not because you do not meet the requirements like other users. But because you cannot handle the requirements at THAT moment. In this case it’s not the solution but can help the symptoms til you get in contact with your ISP to resolve the actual problems at that end of things.

Understanding what “Optimize network for speed” does.History:Originally added when 4.0.6 was launched, this option was designed with intent to reduce latency while in instances by using additional bandwidth and reduced packet sizes, as well as disabling nagling algorithm (selective acks or packet acknowledgements or “naggling”) on application specific level instead of an OS wide hack like the leatrix fix).This option was later hotfixed to be disabled when blizzard realized this feature was not for everyone.In 4.1 this feature was brought back with a toggle so that users had the option to turn it off should they have problems with it. However it is ON by default (important to note this).What it does:Firstly, this feature does same thing leatrix does. It disables packet piggybacking acks to remove any information delay caused by this delay of information. To understand what this means I will use a metaphor. Imagine two people playing catch with a baseball with a guy in middle announcing throw count every 2-3 throws. The information is obtained, but not in realtime. It’s more efficent as it uses less words, but in terms of real time information, inferior. Now imagine instead that announcer is announcing after every single toss. So you get more real time information on throw count, but at the cost of additional words used. Now just substitute baseballs with packets, and words with network bandwidth.That is not all “Optimize network for speed does”. Based on data i’ve collected there is a lot more to it then that. So even people who already had nagling disabled in their OS with leatrix, saw additional reduction in latency with new option as well. It seems the option also uses smaller packets. Being smaller, they are transmitted more frequently. So imagine those 2 catchers were replaced their baseballs with golf balls, and started launching them 3 times as fast. Now you have a much higher throw count.But at even more network bandwidth requirement.This needs citation but nagling alone doesn’t explain things so something else is at work, this is just my theory.This what optimize network for speed does, it makes wow use SUBSTANTIALLY more bandwidth.This feature is only used in INSTANCES. It has no baring on behavior outside of battlegrounds/arenas/dungeons. Regular world servers use old network protocols and not this new option.What is network lag?:Network lag is response time between your computer, and remote computer. This is NOT fps (frames per second). This has nothing to do with graphics lag. These are two different types of lag.Network lag can be caused by ISP problems, bad wiring, bad router, any number of bad equipment problems. But it can also be caused by bandwidth saturation. Your connection is at it’s bandwidth limit and unable to keep up with the demand of network information being sent/received. This guide will only focus on the latter, something we can control with the “Optimize network for speed” option.So is this option right for me?:If you are lagging only in instances, particularly in combat?If you answer yes, chances are you need to turn this option off. Based on extensive data I collected first couple weeks of 4.1. In a 25 man raid, just to give you an impression of what exactly that option really does. with it off I use 16kbps upload and about 160kbps download. With it on, I used 320kbps upload and 480kbps download. Download seemed to use about triple bandwidth with option on, but upload seemed to use 20x the bandwidth and it wasn’t even maxed out cause 320kbps IS my upload cap. So naturally with option on I simply could not raid 25 mans on my 1.2M/320kbps DSL connection. However in 5 mans i was fine with about breaking even latency, and in 10 mans was managable with slightly higher latency then i had with it off. My bandwidth wasn’t capped in 5s/10s but it was high enough to negate the usefulness of the option being on as the additional bandwidth saturation canceled out the benefits and raised latency not lowered it. Just didn’t spike it to point of unplayable lag or DCing like 25s did. Based on data I collected and talking with others I have come up with the following table as a minimum bandwidth requirement I’d say this option needs.5man:.5M download .5M upload10man1M download .6M upload25man1.5M download 1M uploadThis of course is rough estimates so the true test is your latency, if your latency is higher when it on then with it off, then you don’t meet bandwidth requirements for that encounter to have it on. but on another smaller less detailed fight you may get lower latency with it on.What if it’s just certain fights?:Certain fights use substancially more bandwidth then others. One common one brought up a lot is ZG: Venoxis. It may appear the fight itself is bugged since it’s only one that lags you. But you may not have run a 10 or 25 man with enough data yet to compare the results. This fight, although a 5 man, has a lot going on and may be enough to saturate your connection and lag you out with the option turned on. It could also ver well be bugged in a way that makes it use more bandwidth then it probably should. either way, you should turn this option off as at least for me that solved the problem.What if I’m normally fine but tonight my ISP is sucking?This option should also serve as a helper for situations that may arise with ISP. Perhaps your ISP is not getting advertised speeds or is bad during peak hours then good in off hours. So you only lag during these peak hours. You should still turn option off. Not because you do not meet the requirements like other users. But because you cannot handle the requirements at THAT moment. In this case it’s not the solution but can help the symptoms til you get in contact with your ISP to resolve the actual problems at that end of things.