20% bandwidth gain tweak-universal WinX

[wyldfyre]

YES, 20%.... ONE-FIFTH of bandwidth for both your internet connection and your network!!

I have posted this before on the HNU forum, and looked for it today, and could not easily find it, so published a "reminder/for newer members" thread re: same. Felt membership here could really enjoy this as well, so, without further delay, here it is.

**NOTE** If you do not feel comfortable in making changes to your computer and/or network settings, do not perform this tweak. Seek the advice of a more "techie" person, who can easily do this, and may very well enjoy the same tweak themselves. As well, this "newer and revised" version of this tweak contains info not available when I first published it, which is not included in the other quite numerous "copies" circulating "net-wide"..... an HNU and WBU forum "exclusive" from the original "author"..... (as was the original tweak, despite blatant plagiarism which I do not mind at all, as it helps many and "emulation is the most extreme form of flattery", so feel free to distribute this, ad nauseum....)

I consider it a serious tweak, when you think about up to 20% of your usable bandwidth being reserved for Quality Of Service BS, which is not needed for most all connections and/or web applications.

Yes, that was 20%....one fifth of bandwidth!
This trick works with all WindBlows (and a few others even) OS', although the "menus and sub-menus" may differ slightly from the ones described, which are for the "XP, Vista/Longhorn" OS'.

Before performing this tweak, it is imperative that you check and make sure you haven't previously deactivated QoS from the Control Panel. (the usual and common way/tweak before this method)

To do so, go to your Network Connections dialog (in the Control Panel), right click on your connection, choose properties. Under the General or the Networking tab (where it lists your protocols) make sure QoS packet scheduler is checked.

You actually have to have the service ON or ACTIVATED for this tweak to work. Removing it as a service does not re-acquire the 20% reserved for your use!! You MUST have the service ON and ACTIVATED, then set the USE of it to "0" in order to regain that lost 20%!

If needed, you can install the service easily (WindBlows disk not required) by selecting "NEW" from the menu describing the TCIP, File and Printer sharing, and other services. Simply select "NEW" if "Qos Packet Services" does not appear under services for your internet connection (works with LAN and other home networking services too, except you will need to activate/install on ALL computers, and tweak ALL machines, in order for the "extra" machines to benefit from the tweak).


By default, Windows XP (and other older OS') reserves 20% of your available bandwidth for its "Quality of Service" (QoS) applications so it can prioritize certain QoS-aware applications for bandwidth access. This is not only unnecessary in most cases, but it reduces greatly the maximum speeds you get for a particular application, particularly if you're on a fast Network connection.

This 20% minimum can't be removed by unchecking QoS in the network control panel applet. Here's how you can use the Group Policy to change the Reserved Bandwidth:-

1. Log onto your computer with an account that has Administrative rights.
2. Open the Start Menu and click on Run.
3. Type gpedit.msc in the available field and click OK.
4. Once the Group Policy MMC snap-in loads, expand the Computer configuration > Administrative templates > Network > QoS Packet Scheduler branches.

**NOTE** on most machines it will take a moment to expand and load the "Administrative templates" sub-menu to enable you to reach the "Network > QoS Packet Scheduler" folders as needed.

5. Double click on the "limit reservable bandwidth" setting
6. Change the selected option at the top from "Not configured" or "Disabled" to "Enabled".
7. Change The "Bandwidth Limit %" To 0
8. Click OK to dismiss the window, and close the Group Policy Editor.
9. Reboot your computer for these changes to take effect.


**If one wants to "make sure", and engage in "belt and suspenders" certainty that the tweak is implemented and takes full effect...........

but in most cases this is not needed-

you can, while engaged in Step # 7, change the values (all percentages) of "Limit Outstanding Packets" and "Set Timer Resolution" to "enabled" and "0", just like the other setting.

Enjoy the extra 20% bandwidth increase!!

[wyldfyre]

revised previous with larger font to ease/enable clarity in performance of tweak, and to include the new tips and info that were not included in the original postings of the tweak. (on the HNU forum)

This tweak should work well with any "broadband" access (satellite included), but beware of your FAP constraints, and set "FAPMON" accordingly once you have calculated and gotten used to the speed increases. (if you don't have it you should get it free from the forum downloads section).

The increase is exponential- the more speed you already have, the more you gain by increasing the existing speed by one-fifth. Modem/"built-in" software and such may CAP those speeds.

So, if you reach your "cap" limitations, at least you are assured of M$ or no one/thing else depriving you of 20% of what you pay for. Unnecessarily, may I add.

Again, ENJOY, FOLKS!!!!


"stay tuned" for Vista/Longhorn specific tweaks by yours truly upon release and common usage of the new OS'.

am already working on them.

but this one seems to work just as good with the "beta", both released to public betatesters and the "pre-beta" not released versions I have. Same process/menus, I have found no difference except the graphics for the menus. Tested pre-tweak to tweak results on the newest "pre-release" betas of both Vista and "Business" versions revealed exactly identical increases as the tweak applied to XP home, pro, and media center versions, OEM and not, and with SP's 1, 2, and 3. (consideration by M$ to reviving the "Longhorn" moniker for biz and server versions is being considered, so the "pre-beta-releases" are not even designated except as numbers)

Again, if one feels uncomfortable in doing such things, seek the aid of your local geek, who will love the ease and effectiveness of this tweak and will "spread the wealth", so to speak

[Bluetrue]

gpedit.msc is only available in XP Pro. Is there a way to do this in XP Home? Thanks.

[wyldfyre]

I will research same and get back to you. I do not have, and have never used, a "HOME" edition of WindBlows.

Perhaps there are others on the forum who have experience in "HOME" versions who can answer this?

I would think it should be available in some way, but perhaps not....

I apologize for not being able to furnish you with an immediate answer to your question!

[wyldfyre]

credit to "bbfuzz" for bringing this to light:

Quote:
Originally Posted by bbfuzz
In your writeup do I do this to the satellite qos in settings and also the LAN settings also since I am the mother ship on the network and share the connection with two wired and two unwired machines.


CORRECT.

and in order to enjoy similar benefits on all other machines, this tweak need be applied to each and every machine networked.

As well, once this tweak is applied to ALL machines on the network, each machine will enjoy a corresponding increase when interacting with any other machine, as this tweak affects not only net access, but the interactive quality of all machines connected to those which the tweak has been applied to. (if one applies the QoS tweak universally)

once applied, try it out and stress it to the utmost...and re-post and let us all know how well it worked for you!

If you have any questions concerning proper application of the tweak, feel free to use PM or Email as provided on the forum so I may assist you in performing this tweak (same for anyone else who does it).

A 20% increase in usable bandwidth is a serious deal, in my way of thinking, and if I may serve in furnishing such gains in BOTH net access AND networking then I am happy to do so, as this is a d@mn3d serious increase!

(for some "networked" machines the 20% gain will be DOUBLED if the networked machines are furnished with this tweak, net access only showing a 40% increase in throughput (if not "capped" by your access to the server or by the network cards/capabilities of the server and the receiving machine) , "non-online" network interaction with designated server increased by 20%)

[Bushytails]

Do you have some "before" and "after" numbers on upload/download speeds over a satellite connections? Otherwise this seems a bit high on the "yeah, right" scale.


--Bushytails
(Who is quite happy never having to see windows except on other people's computers!)

[grover92000]

From Microsofts KB (http://support.microsoft.com/kb/316666):

Windows XP Quality of Service (QoS) enhancements and behavior
...
Correction of some incorrect claims about Windows XP QoS support
There have been claims in various published technical articles and newsgroup postings that Windows XP always reserves 20 percent of the available bandwidth for QoS. These claims are incorrect. The information in the "Clarification about QoS in end computers that are Running Windows XP" section correctly describes the behavior of Windows XP systems.

[Midway]

I remember this "tweak" coming out not long after XP went gold. Since then it has been shown not to be effective. Just do a google search on "QoS tweak" and you will find plenty of refutes against this tweak. Here is a few links I found on the first search page:

http://www.tweakhound.com/xp/xptweaks/supertweaks9.htm

http://mywebpages.comcast.net/SupportCD/XPMyths.html

http://www.tweakxp.com/article37125.aspx

[wyldfyre]

**am working on a "fix" for Home versions not having a group policies editor. !!!see below!!!

M$ asserts that QoS does not reserve 20% bandwidth on a constant basis, but is "as needed". Supposedly, commands "check" to see if the Quality of Service Packet Scheduler is needed, and "instructs" the machine to "release" if not needed. Sorry, M$, but it does NOT work that way!! (and I can only believe they are well aware of it) Even if those commands WERE used, (and most times the PATH and RESV refresh messages are NOT sent over the connection, as "M$ auto-update", the primary service utilizing "QoS" DOES NOT send or reply to same, and I am unaware of any app/service that DOES) the release and reconfiguration would not and can not occur WITHOUT RESTARTING THE OS. Of course, upon restart, "QoS" is AGAIN "ON", checking to see if it is needed!!! Many folks make the error of depending on M$ stuff to work properly. Or for M$ to consistently publish accurate information. I will not speculate as to the wisdom of such expectations. Nor will I speculate as to WHY M$ wishes to have any bandwidth reserved for their own purposes. (QoS does not serve any useful function for home or business users that anyone has ever seen)

The fact that QoS could theoretically be "released" by PATH and RESV refresh messages causes much confusion concerning this tweak. Lacking the information that it would require OS restart to release the reserve, and that M$ (or the very few apps utilizing QoS) do NOT transmit or respond to PATH and RESV refresh messages/queries, one COULD mistakenly think that it MAY BE the "Urban Legend" M$ makes the tweak out to be.

This is why "cutting off or eliminating" QoS does NOT work. This is why the service must be ON, but the reserved bandwidth setting decreased. Even if the service is turned OFF, it does NOT release the reserve, due to lack of the PATH and RESV refresh messages, and because an OS restart is needed for the reconfiguration process.

**If one does happen to utilize an app/service which uses QoS and may be dependent on the Packet Scheduler service, simply set the percentage to 1 or 2 percent as opposed to the 20% original setting!!

(note- reducing or eliminating "QoS" reserved bandwidth does not affect the operability of M$ auto-update, as they fail to include or respond to any PATH or RESV refresh messages in communications with machines, anyway. Likewise, "error reporting" services, etc, which most people cut off anyway, are unaffected as well.)

By my own investigation/testing, I verified that the M$ "QoS Myth" assertions are indeed not the case. By using any decent "speed-metering" software, besides "speed tests" on different servers, (and my own) the difference is immediately apparent. Considering the "wga/wpa" and like spyware, which does make use of QoS (but NEVER transmits or reacts to the PATH or RESV commands that THEY SAY ensures there is no bandwidth retained by QoS), it does NOT take Steven Hawking to figure out WHY they have not only turned the tweak into "myth", but INTENTIONALLY made things so that simply disabling the service STILL RETAINS the reserve!!

I would point out that, with all the literally thousands of "XP tweaks" out there, M$ feels it NECESSARY TO:
!. engage in PR to dispute this little tweak- &.....
2. insert the process into the OS in such a way that simply disabling the service DOES NOT release the reserve....
Let the reader speculate for themselves as to the reasons behind same.

We all have had a laugh at "toast.net's" generous metering from time to time. On all my machines, "toast.net" had to greatly extend the graphic chart to be able to give me a "reading". First time I ever saw that happen.;-)

Honestly, besides the obvious bandwidth gain, I do not want my machines transmitting ANY info (QoS or otherwise) that I do not instruct it to.

Once the tweak is done, one may be able to "tweak" (using your fav software such as TCP Optimizer, etc) for higher RWIN and other values as well. Once I tweaked and "re-tweaked", even the older 700mhz 'top will "peg out" a lot of "online speed test" servers.

**One must keep in mind my results are NOT typical. I have went through the trouble of having fresh drops from the cable circuit installed (of 100% triple-shield cabling), installed special splitters, auxiliary grounding system, etc- in other words, anything to improve/solidify the feeds, and result in unquestionable reliability and no interference from some pretty powerful RF equipment I have. So these would reflect the most optimum test conditions possible, and again, NOT satellite but cable, which (usually) would provide a pretty stable "average standard speed reading" to start with.

I can tell you I do this to each and every machine I have and/or service, and have never had one problem arise. Quite the opposite, I have had many "word of mouth referrals" resulting from a serviced machine being MUCH faster than a neighbor's or friends.

It is important to realize that one cannot hope to exceed the "speed limits" of the ISP server/lines/other hardware one is connected to. Tweaks only allow one to maximize AVAILABLE throughput. (even though my results far exceed the stated "maximum speed" RoadRunner offers for my account by more than double)

[wyldfyre]

ALWAYS BACKUP REGISTRY BEFORE EDITING. A "restore point" is useful as well. This applies to ANY editing of the registry for any purpose.



HKLM\ Software\ Policies\ Microsoft\ Windows\ Psched\ Modify

NonBestEffortLimit (DWord) - If it is not there,create it.

The Value is the percentage reserved. Set that to "0" (zero)

**or set to 1 or 2 % if you may be one of the few who NEED QoS. Haven't met anyone yet, but there must be someone.....

**BTW- WGA/WPA (or whatever they may be calling this spyware crap this week) is one of the apps that use QoS.

To me, another good reason to rid my machines of this unnecessary nuisance.

[wyldfyre]

Originally Posted by Midway

I remember this "tweak" coming out not long after XP went gold. Since then it has been shown not to be effective. Just do a google search on "QoS tweak" and you will find plenty of refutes against this tweak. Here is a few links I found on the first search page:

http://www.tweakhound.com/xp/xptweaks/supertweaks9.htm

http://mywebpages.comcast.net/SupportCD/XPMyths.html

http://www.tweakxp.com/article37125.aspx

**NOTE**
They either DIRECTLY QUOTE M$, or offer no explanation at all except to assert "About the QOS "tweaks" floating around the net. Ignore them, they don't work!" (tweakhound)

I am always highly amused at sites that directly quote M$, or "copy and paste" tweaks/myths/etc. without their own independent and unbiased research and experimentation to verify one way or the other.

M$ $ez "WGA/WPA will eliminate piracy and the savings can then be passed on to the consumer", too. (ref: other threads on-forum)

The dependency of wpa/wga type spyware crap on QoS (one of the few services utilizing same) is enough in itself for me to take it out of anything I own, even if there was no "substantial gain"......

besides savvy "virus developers" having bandwidth to do their work in, without most users being able to detect it.... QoS is not one bit more secure than any other part of WindBlows.