Re: performance: store.exe uses 579Mb only out of 4Gb



"/NoExecute=OptIn" should be optout, but that's not the problem; it's merely
a source of other potential problems (loading the PAE kernal on 32 bit
exchange is a bad thing)

RAM is mainly used by store.exe in the form of database page buffers. The
number of buffers, and hence the amount of RAM used, is controlled by the
parameter msExchESEParamCacheSizeMax of the object
Services/Microsoft Exchange/Your organization/Administrative Groups/Your
administrative group/Servers/Server name/Information Store, and the
recommended values are as follows:

. The recommended size on servers with the /3GB switch set: 229376
(896 MB)
. The recommended size on servers without the /3GB switch set: 147456
(576 MB)
. The recommended maximum value: 311296 (1.2 GB)
. The recommended value on large address-space constrained servers:
196608 (768 MB)
The value is in incremets of 8K and should be set on a 32M boundary.



You'll find more information on optimizing memory for Exchange in:

http://support.microsoft.com/kb/325044/en-us

579M soundls like a value that would be used if you were not using the /3gb
switch, but again I doubt that's going to be the performance issue.

Log buffers could have an impact on write latency as well, and you'll want
to follow the recommendations of the referenced article.

The fact that you're using optin implies that you have a server based on
PCIExpress with the old problem of a large address window. This causes RAM
to report as either 3.25GB or 3.5 GB when you have 4GB installed. The usual
response from the vendor is to do something to enable PAE, aka optin (you
know this is the default by the way, so why the heck is it in there?). The
problem with enabling PAE is that:

1. Exchange is not AWE aware nor PAE aware and can't use it.
2. Enabling PAE causes each page tabke entry to consume twice as much RAM,
effectively halving the number of available PTEs; a resource which is
already constrained on an exchange server. This decreases the number of
connections/users the server can support and increases instability.

I see you're using a NetApp SAN, which is a good start :-), but in small
environments it's easy to provision two few spindles and end up in an
undersized state. Probably the most common problem is when you create only
one aggregate and carve everything from there. In that case, an IO
intensive process against the databases can impact Log IO - an example would
be backup verification. How exactly is the storage configured? You mention
that you're using the iSCSI software initiator, but don't give any deatails
on the connection. Certainly, with only 115 mailboxes, it would be
extremely difficult to saturate a 1G3 connection with the iSCSI traffic
alone. How is the network configured? have you enabled jumbo frames? is
the nework on which you are running the iSCSI traffic isolated? I think
investigating the storage will lead to the answer to your latency issue..

"George" <George@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:D3F93969-C9A7-4BA7-A436-863EFA0B807B@xxxxxxxxxxxxxxxx
I have an exchange 2003 sp2 server that seems to be having a lot of free
RAM
~2.8Gb out of 4Gb and the boot.ini file is as below. Should I have so much
free RAM is the server hold hundreds of mailboxes? store.exe is using only
579Mb - the machine has two 2.8Ghz Zeon processors and stores its data on
our
NetApp SAN using iSCSI(ms software initiator).

my boss is constantly complaining of slow speed when moving e-mails etc
and
from what I can see in the exchange user monitor the maximum server
latency
in ms is 71; the database is 63Gb(edb) and the accompanying stm file is
16Gb
and holds 115 mailboxes. there is another database on the server that hold
175 mailboxes limited to 300Gb, which is 10Gb plus 3.6 for the stm file.

[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(2)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Windows Server 2003,
Enterprise" /fastdetect /3GB /Userva=3030 /NoExecute=OptIn

is the file configured OK?

--
G


.



Relevant Pages

  • Re: SBS 2003 Premium R2 server becomes more unstable, page file gr
    ... Les Connor [SBS MVP] ... I haven't done anything to exchange, ... >>> according to MS specs and your suggestion of the PF being 1.5x the>>> RAM ... The server hasn't crashed yet, but it has in the past. ...
    (microsoft.public.windows.server.sbs)
  • Re: Debate in downsizing the RAM on Exchange Server
    ... > the removal of 1GB RAM. ... > other problems in the server or Exchange. ... Exchange is running on a DC. ... More physical memory should help ...
    (microsoft.public.exchange.admin)
  • Re: Store.exe consumes too much RAM
    ... report our server as uninfected. ... SBS2000, Exchange 2000, SQL Server 2000 all with latest ... >server has been down as low as 4k of available memory. ... >out of the installed 1GB of RAM. ...
    (microsoft.public.exchange2000.information.store)
  • Re: Large amounts of RAM (>4GB) in a 32-bit TS server and PAE
    ... My work currently has a single TS server and it is bogged down, ... It has 4GB of RAM. ... There has been lots of discussion on why PAE might be *bad* on a server ... 2GB kernel space). ...
    (microsoft.public.windows.terminal_services)
  • Re: Is it possible to redirect the default user shares?
    ... have Server based file and email AV (mostly ... Particularly, any system with Exchange ... SBS has a max of 4GB RAM. ... Most of our SBS2003 Standard sites have 10-20 users, our Premium sites ...
    (microsoft.public.windows.server.sbs)