G
Glenn Goodwin
Hello - I have noted a lot of posts about SERVICES.EXE consuming large
amounts (100, 200+ MB) of memory on startup which remains that way for
the time the server is up.
I recently experienced this issue and believe I have found a solution
that doesn't appear to of been specifically mentioned in any posts.
Sometimes the memory usage of SERVICES.EXE should be large (even on
reboot) due to optimization settings for a server. See 'The
LargeSystemCache Tuning Knob section' in -
http://www.microsoft.com/technet/prodtechnol/windows2000serv/maintain/optimize/wperfch7.asp.
i.e. By changing the network settings from 'Maximize Throughput for
File Sharing' and 'Maximize Throughput for Network Applications' to
'Balance' in Networking->File and Printer Sharing...->Server
Optimization the SERVICES.EXE reduced in size after a reboot -
previously on my server it was 200MB on a 2GB physical memory server.
If you actually performance monitor the SERVICES.EXE process you'll
notice that the 'Working Set' is 200MB while the 'Private Bytes' is
only 7MB. This is the difference between memory that has been
reserved for a performance gain and memory that is actually being
used.
I saw this behaviour a Windows 2000 Advanced Server running 2GB of
physical memory.
Thanks
Glenn Goodwin
amounts (100, 200+ MB) of memory on startup which remains that way for
the time the server is up.
I recently experienced this issue and believe I have found a solution
that doesn't appear to of been specifically mentioned in any posts.
Sometimes the memory usage of SERVICES.EXE should be large (even on
reboot) due to optimization settings for a server. See 'The
LargeSystemCache Tuning Knob section' in -
http://www.microsoft.com/technet/prodtechnol/windows2000serv/maintain/optimize/wperfch7.asp.
i.e. By changing the network settings from 'Maximize Throughput for
File Sharing' and 'Maximize Throughput for Network Applications' to
'Balance' in Networking->File and Printer Sharing...->Server
Optimization the SERVICES.EXE reduced in size after a reboot -
previously on my server it was 200MB on a 2GB physical memory server.
If you actually performance monitor the SERVICES.EXE process you'll
notice that the 'Working Set' is 200MB while the 'Private Bytes' is
only 7MB. This is the difference between memory that has been
reserved for a performance gain and memory that is actually being
used.
I saw this behaviour a Windows 2000 Advanced Server running 2GB of
physical memory.
Thanks
Glenn Goodwin