Stopping Services for better gaming

Status
Not open for further replies.
Originally posted by StormBringer
I have a AMD Athlon XP 1600+ and 1536MB DDR, and a GeForce2 MX 400 64MB DDR and there is no noticable difference when I shut down all services that aren't absolutely necessary and when I run as normal. I haven't run any benchmarks to see the actual difference but it has absolutely no noticable impact on any of my games or applications.

With that much memory you can't really expect to have a noticable difference. We're only freeing up around 50MB of memory, and I have a hard time believe a game can take up 1.5GB of memory space, so you have plenty of memory to go around. Still every little bit helps. The best thing you can do is the upgrade your graphics card.

P.S. Thanks for the tip Rick, I thought there was another way to go about it. :)
 
You misunderstood my intent SuperCheetah, my point was that while my performance doesn't seem to change, there is nothing wrong with it. I am perfectly happy with my graphics card also. I was just trying to point out that if you simply add RAM, you can avoid the hassle of stopping and starting services.

Often people overlook the importance of RAM and go for the fastest CPU, but as most of us know, it doesn't matter if you have the fastest CPU, if you don't have much RAM, your system won't perform as well as a slower CPU with a lot of RAM.
 
Originally posted by StormBringer
You misunderstood my intent SuperCheetah, my point was that while my performance doesn't seem to change, there is nothing wrong with it. I am perfectly happy with my graphics card also. I was just trying to point out that if you simply add RAM, you can avoid the hassle of stopping and starting services.

Sorry if I misunderstood you StormBringer. The reason for making this batch file is to make it easy to turn the services and background tasks on and off without much hassle. Not everyone has the money to buy extra memory so this is an easy way to gain some extra memory while gaming or doing some other task. Believe me I know how important RAM is to a system, that is why I'm taking the time to make this batch file.
 
I often leave mIRC running when I play so this wouldn't really be a good idea in my case. Stopping the DNS service & a few others will make me loose my internet connection until I start them over.
 
This was what I knew was going to happen at the beginning:- people begin killing off tasks one by one, and lose all of the extra functionality they have spent time adding. I don't personally see the point of removing stuff that you actually use. i.e. removing services that you don't need is a good idea, but why not just stop them from starting permanently, rather than running a .bat file to kill them all the time.
 
I think what could make this better is if there is a way to make it faster. It takes awhile to turn off my services.. Maybe 1 per every second or so and some of them ask me if I'm sure I want to turn them orr or not which consumes more time.

If I'm not mistaken, there is a registry tweak that removes the delay on stopping services. Perhaps this would speed up the batch file's progress. And, there is probably a switch of some sort to shutoff services without asking for the user's consent. This could really enhance the batch file.
 
Originally posted by Th3M1ghtyD8
This was what I knew was going to happen at the beginning:- people begin killing off tasks one by one, and lose all of the extra functionality they have spent time adding. I don't personally see the point of removing stuff that you actually use. i.e. removing services that you don't need is a good idea, but why not just stop them from starting permanently, rather than running a .bat file to kill them all the time.

I personally have already done this. Most people don't really know what the services do so they don't mess with them, hell I didn't until I started doing this.

I agree Rick, it takes alot of time to kill my services too, I plan on investigating this more and see if there is a fix.
 
Here is a quick little update. I found a way to cut down on the service kill time.

Here is what you want to go to:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WaitToKillServiceTimeout

The default setting is 20000 or 20 secs, setting it to 5-10sec should do the trick (that's 5000 to 10000).
 
Status
Not open for further replies.
Back