Re: Exchange server super duper slow
- From: "Dave Nickason [SBS MVP]" <gwdibble@xxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 12 Aug 2008 12:48:11 -0400
I'd start by moving the page file and see if that helps. Page file settings are the subject of a religious war, but personally, I'd match the existing settings, but on the other drive. Leave a 16 MB page file on C - that's more than enough for a small crash dump - at the same time, you could look in Startup and Recovery to make sure the system is configured for small memory dumps.
I've never been that close to the store size limit, so I'm not sure how or why that would effect performance - that limit is a licensing thing, so I don't think store size alone would cause a performance issue with anything unrelated to Exchange itself. However, that server is not using an unexpected amount of RAM for store.exe - mine with 4 GB is currently using 653 MB and the performance is fine.
I would look at whatever else is using a lot of RAM. It's possible you have SQL instances that are hogging a bunch of RAM unnecessarily. I've heard of plenty of instances where people have had good results throttling SQL RAM usage on SBS (including my own production box), but never where anyone benefitted from messing with Exchange. Exchange is designed for that to be unnecessary.
In reading through the other posts, I thought Matt made a good point about the RAID. It seems that your results in restarting the information store rule out a degraded array, but I'd look at that anyway, just in case.
My server, with about 20 users logged in, is using about 3.3 GB of its 4 GB RAM. That's about where it runs. If you look in Task Manager and it appears that this box is starved for RAM, I'd look at what other apps are using an unexpectedly high amount. You can narrow down the SQL instances by getting the PID from Task Manager. Then open a cmd prompt and run "tasklist /svc" - find the PID, and the output will tell you which instance it is.
"Trent Hewitt" <TrentLHewitt@xxxxxxxxx> wrote in message news:50986d61-d834-4f0f-a132-081eb6e6527e@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
thanks for all the responses. I work for many different companies so
this particular server i end up working with over remote desktop. When
I log in via rdp, it takes about 5 mins (and sometimes i get booted)
before i am taken to my desktop. When I am in, the performance is
nothing short of horrible. Not long ago, i logged in and stopped the
information store service; after that the server was operating as it
should, so i believe that i have narrowed down the problem to the
store process.
This company has workers worldwide; some use Outlook, some Entourage
and others OWA. Most of the complaints come from users using OWA which
is kinda like working directly on the exchange db.
My page file goes like this:
paging size for all drives is 2046-4092 on the C drive....which I have
just noticed has just barely over a GB of space. I am going to move my
page file to my D drive which as over 200g of space. When I do that,
what size should i set the paging file to be? Or should it be set to
system managed?
As for when they get over 75g, I have purchased and R2 transition pak
and exchange 2003 enterprise.
Thanks for all the help
Trent
.
- Follow-Ups:
- Re: Exchange server super duper slow
- From: Trent Hewitt
- Re: Exchange server super duper slow
- References:
- Exchange server super duper slow
- From: Trent Hewitt
- Re: Exchange server super duper slow
- From: Dave Nickason [SBS MVP]
- Re: Exchange server super duper slow
- From: Trent Hewitt
- Exchange server super duper slow
- Prev by Date: Re: Exchange server super duper slow
- Next by Date: Re: SBS 2003 OWA Problem
- Previous by thread: Re: Exchange server super duper slow
- Next by thread: Re: Exchange server super duper slow
- Index(es):
Relevant Pages
|