Discussion Locked

E2K performance degrades until reboot

0 helpful
6 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

We have our E2K server hosted at a place with T3, on a pretty hefty DL380 (although the transaction logs do not go to a separate disk. We have a T1 at the office with almost all users using W2K Pro and Outlook 2000, a couple with Win98 and Express-although that doesn't seem to matter.

I am having to reboot the server each morning to keep up performance. The server seems okay and i can always get on it through pcanywhere. 1.80GB free space. As performace goes down, users have timeouts tothe server or Outlook takes forever to talk with the server and bring up the next message to read or send. After a reboot it behaves normally again. Sometimes I can just tell the user (or me) to reboot PC and Outlook works a bit better. This problem seems to have gotten worse the last couple weeks. Unfortuneately I have no tools to watch my backbone yet, although high traffic on either side doesn't explain why a E2K reboot helps. All help very much appreciated!

Regards,
David

6 replies

by timthetoolman

Hi,

It sounds more like a server problem than a network problem and my guess would be that your server is short on memory.

But even if that isn't the problem you should run the performance monitor on it during the day - with a log file. And analyse the results at the end of the day.

You will almost certainly see something increasing over the day. As I said, my guess is that it will be pagefile usage...

Oh, and you can monitor network traffic with that too...

Hope this helps,
Cheers,
Tim.

by timthetoolman

Oh, I should mention. Add the following counters at a minimum. Process, Processor, system, paging file, memory and you may want to add some exchange counters too.

I wouldn't sample any more often than once every 5 mins. Disk usage for this will be reasonably heavy.

Cheers,
Tim.

by a.grogan

How much memory does your server have - if it is above 1GB - add the following switch into the boot.ini /3GB - this will slow memory fragmentation down.

This discussion is closed to new replies.