Some VS.Net related System proccesses I don't recognize? Any help?

D

Denaes

Senior Contributor
Joined
Jun 10, 2003
Messages
956
aspnet_wp.exe is at the top of my list now with 20,404k followed by NOPDB.EXE with 13,172k.

SERVICES.EXE is now 9,220k.

I just installed two days ago the VS.Net (I had VB.Net Standard before) and yesterday I installed MSDE (mini SQL Server).

Call me anal retentive, but I don't like services/processes eating up my CPU time/ram if I don't use or need them.

Actually as I go through there, I'm a little pissed.

I burn a cd like once a week or month and Directcd.exe is keeping a process open all the time at 3 megs.

3 megs or even 15megs isn't a huge amount when you have 512mb of Ram, but when you have 8 services totaling about 120mb, thats nearly a ram upgrade right there being wasted.

Can anyone tell me if aspnet_wp.exe, NOPDB.EXE or SERVICES.EXE are required for SQL Server or vs.net?

aspnet_wp.exe looks like it might be used for running asp.net (.aspx) on an actual webserver or something.

I'm going to google around for a list of common services and what to shut off/keep.

call be crazy, but I'd rather wait that extra second or three for software to load up than keeping it hanging in memory for weeks on end "just in case". I'll open an app if I want to use it, thank you :D
 
services.exe is the generic windows exe that hosts a lot of OS related services - definately required.
aspnet_wp.exe is the service that provides asp.net functionality to IIS so is required if asp.Net is in use.
 
You can't terminate instances of the service.exe process. You can stop the services that are hosted in it however.

As for aspnet_wp.exe you can terminate that whenever the urge arises. It will be restarted automatically by IIS when needed.
 
that memory process is the exact reason why I don't use Directcd anymore. Its jsut not necessary.

But I can't talk, right now I have only 500MB of ram free (out of 1GB), and I'm only running outlook and IE. God knows what all those processes are now...
 
IE gets absurd in terms of ram. I can't think of why IE should take up between 30 and 120 mb of ram... just sometimes I have to close all the windows and reopen them to free up memory.
 
it used to be a lot worse, I remember leaving IE open overnight a couple of years ago and memory leaks eating up all the ram into it would crash.

At least IE consistantly uses up ALL the ram now :);)
 
Back
Top