This is one of the solutions I was reading online. Some users were saying it did nothing, others reported it to work. Some said it worked on their 32 systems, but not on their 64.Aphasia wrote:Take a look on if the Multimedia Class Schedular is active, becuase if it works as it did in Vista, it will trottle some things as long as you have any media application running. Although it usually throttles high bandwidth things, i cant say that it wouldnt effect other things as well. The easiest way to disabled it by setting a few values in the registry, since other services require the MMCS to function.
FubbHead wrote:Actually, I just wondered if Windows Vista/7 uses QoS to throttle the traffic, or if it's more low-level than that (IRQ-routing, etc, etc).
Aphasia wrote:Even Steam counts as a media application with regards to the class schedular, so, it depends. And i did a rather heavy work on it, and if you set it correctly in the registry, it doesnt throttle. Easy as that. What started it all was getting a very low through put against my file server. When i finally narrowed it down to the fact that if winamp, wmp, skype or steam was started, i got crappy throughput in one direction, it nailed it. So with crappy i mean 13MB/s, after the registry entry, 110MB/s+
Thats the difference it can make with and without throttling.
Users browsing this forum: Google [Bot], Google Adsense [Bot] and 3 guests