should i be rebooting w2000?

[tmmm]

hi all

I was wondering if it best practise to reboot w2000 server every so often?

I know win nt needed a reboot from time to time.. I run a fairly demanding
help desk application on the server and I notice it tends to bog down and
really slow up ocassionally..

should I be rebooting w2000 every couple of months?

what are your thoughts on this..

thnx

tm

 

[Pegasus \(MVP\)]

Adopt the pragmatic approach: If it improves performance,
do it, otherwise, don't.

 

[Greg Stigers]

I would encourage you to try to determine why your fairly demanding help
desk application tends to bog down and really slow up occasionally. You can
use Task Manager or System Information's System Summary to take your own
snapshot of the system state. The latter will allow you to print it, or save
it as a text file or system information file, which beats trying to remember
what it said last time you checked. Or, you can set up the Performance
Console. Either way, you can try to track degradation of performance or
resource allocation over time. If you find it, work with your fairly
demanding help desk application vendor to figure out why they are throwing
away perfectly good resources.

 

[*Vanguard*]

"tmmm" said in

I know win nt needed a reboot from time to time..

I remember with MS came out with a patch that revealed their uptime counter
would overflow after something like 4 months which would crash or hang
Windows NT4. When I asked around, no one had encountered the problem.
That's because no one could manage to keep WinNT4 Server up that long.

demanding help desk application on the server and I notice it tends
to bog down and really slow up ocassionally..

When it slows down, have you checked the Task Manager under Processes to see
what is sucking up all the CPU? Or is there a lot of local drive activity
with low CPU usage?

should I be rebooting w2000 every couple of months?

Instead you might want to consider running the process at a higher priority.
It probably loads and runs at Normal priority. So up it to Above Normal
priority (or High if it is your super critical application, but don't use
RealTime as the application could make it impossible to use your desktop and
even Windows might appear to hang).

what are your thoughts on this..

The other suggestion to watch Task Manager to check the CPU usage for your
process and to monitor the memory usage and to see if you're getting low on
real RAM and having to allocate more page file space, along with using the
Performance Monitor will help you determine if there is a memory leak, if
your process or something else is sucking up the CPU, if you're having lots
of disk thrashing either because of too little system RAM and having to use
more pagefile space or because something else is swamping the drives.