Store.exe limited but still growing - Microsoft Exchange

This is a discussion on Store.exe limited but still growing - Microsoft Exchange ; I have limited the store cache size to 262 MB (See Microsoft Knowledge Base Article - 266768 and set the msExchESEParamCacheSizeMax = 65536). I restartet the server and waited. Now after a few days, the store.exe is still growing (Taskmanager ...

+ Reply to Thread
Results 1 to 4 of 4

Store.exe limited but still growing

  1. Default Store.exe limited but still growing

    I have limited the store cache size to 262 MB (See
    Microsoft Knowledge Base Article - 266768 and set the
    msExchESEParamCacheSizeMax = 65536). I restartet the
    server and waited. Now after a few days, the store.exe is
    still growing (Taskmanager shows 336 MB). I have an
    Exchangeserver 2000 with SP4. Can anybody help me?

    Thanks


  2. Default Re: Store.exe limited but still growing

    Simon -

    You have not mentioned why you lowered the cache to such an extraordinary
    low value. You did mention any virtual memory error events, like the
    9582's. Please keep in mind that just because the Store.exe appears to be
    using a lot of physical and virtual memory (working set and virtual bytes),
    does not mean you should lower the cache to something like 262MB. By doing
    so, you are putting a lot more pressure on the disk subsystem, which in many
    cases will lead to other kinds of undesired things... for instance, disk
    bottlenecks (latecny, etc.). The lowest value I would recommend lowering
    the cache to would be "147456" (= 576Mb). This is the Exchange Product
    Group's recommended minimum. It's good to use on Windows 2000 Standard
    Servers that can not use the /3GB switch and severe VM-constrained servers.
    Which leads me back to my original thought... you did not mention the 9582
    Events in the Application Event Viewer Log.

    I would suggest you do not adjust this cache unless you need to. I would
    recommend you remove the value in AD, so the value reads "Not Set", allowing
    the Store to use the default size of 858Mb. That default cache is mapped in
    the virtaul address space, where each process gets 2GB of virtual addresses
    to use (regardless of how much RAM is installed). That VA space can be
    increased from 2GB to 3GB by placing the "/3GB" switch in the boot.ini
    provided: 1] the server has 1GB RAM or more; and 2] the OS is at least W2K
    Advanced or any version of W2K3.

    In summary, if the Store is generating 9582 events then the cache can be
    adjusted to combat the problem.

    For more details on the Virtual Memory Fragmentation issue and store cache,
    please see my most recent weblog entries at the MSDN site:
    http://blogs.msdn.com/mfp2

    Hope this helps.

    -------------------------
    Michael Palermiti
    Enterprise Messaging Support

    This posting is provided "AS IS" with no warranties, and confers no rights.
    © 2004 Microsoft Corporation. All rights reserved.


    "Simon" <skarrer@nexustechgroup.com> wrote in message
    news:148701c3fbb6$90fdd600$a401280a@phx.gbl...
    > I have limited the store cache size to 262 MB (See
    > Microsoft Knowledge Base Article - 266768 and set the
    > msExchESEParamCacheSizeMax = 65536). I restartet the
    > server and waited. Now after a few days, the store.exe is
    > still growing (Taskmanager shows 336 MB). I have an
    > Exchangeserver 2000 with SP4. Can anybody help me?
    >
    > Thanks
    >




  3. Default Re: Store.exe limited but still growing

    EDIT: My second sentence should read: "You did NOT mention any virtual
    memory error events, like the 9582's"

    Sorry,

    Michael Palermiti
    Enterprise Messaging Support

    This posting is provided "AS IS" with no warranties, and confers no rights.
    © 2004 Microsoft Corporation. All rights reserved.


    "Michael Palermiti [MSFT]" <michaelp@online.microsoft.com> wrote in message
    news:%23DxwJ17%23DHA.4072@tk2msftngp13.phx.gbl...
    > Simon -
    >
    > You have not mentioned why you lowered the cache to such an extraordinary
    > low value. You did mention any virtual memory error events, like the
    > 9582's. Please keep in mind that just because the Store.exe appears to be
    > using a lot of physical and virtual memory (working set and virtual

    bytes),
    > does not mean you should lower the cache to something like 262MB. By

    doing
    > so, you are putting a lot more pressure on the disk subsystem, which in

    many
    > cases will lead to other kinds of undesired things... for instance, disk
    > bottlenecks (latecny, etc.). The lowest value I would recommend lowering
    > the cache to would be "147456" (= 576Mb). This is the Exchange Product
    > Group's recommended minimum. It's good to use on Windows 2000 Standard
    > Servers that can not use the /3GB switch and severe VM-constrained

    servers.
    > Which leads me back to my original thought... you did not mention the 9582
    > Events in the Application Event Viewer Log.
    >
    > I would suggest you do not adjust this cache unless you need to. I would
    > recommend you remove the value in AD, so the value reads "Not Set",

    allowing
    > the Store to use the default size of 858Mb. That default cache is mapped

    in
    > the virtaul address space, where each process gets 2GB of virtual

    addresses
    > to use (regardless of how much RAM is installed). That VA space can be
    > increased from 2GB to 3GB by placing the "/3GB" switch in the boot.ini
    > provided: 1] the server has 1GB RAM or more; and 2] the OS is at least W2K
    > Advanced or any version of W2K3.
    >
    > In summary, if the Store is generating 9582 events then the cache can be
    > adjusted to combat the problem.
    >
    > For more details on the Virtual Memory Fragmentation issue and store

    cache,
    > please see my most recent weblog entries at the MSDN site:
    > http://blogs.msdn.com/mfp2
    >
    > Hope this helps.
    >
    > -------------------------
    > Michael Palermiti
    > Enterprise Messaging Support
    >
    > This posting is provided "AS IS" with no warranties, and confers no

    rights.
    > © 2004 Microsoft Corporation. All rights reserved.
    >
    >
    > "Simon" <skarrer@nexustechgroup.com> wrote in message
    > news:148701c3fbb6$90fdd600$a401280a@phx.gbl...
    > > I have limited the store cache size to 262 MB (See
    > > Microsoft Knowledge Base Article - 266768 and set the
    > > msExchESEParamCacheSizeMax = 65536). I restartet the
    > > server and waited. Now after a few days, the store.exe is
    > > still growing (Taskmanager shows 336 MB). I have an
    > > Exchangeserver 2000 with SP4. Can anybody help me?
    > >
    > > Thanks
    > >

    >
    >




  4. Default Re: Store.exe limited but still growing

    Thanks Michael for the information, but how can I
    restrict the memory use of exchange? We have just 10
    users and there are some other programs running.

    >-----Original Message-----
    >EDIT: My second sentence should read: "You did NOT

    mention any virtual
    >memory error events, like the 9582's"
    >
    >Sorry,
    >
    >Michael Palermiti
    >Enterprise Messaging Support
    >
    >This posting is provided "AS IS" with no warranties, and

    confers no rights.
    >© 2004 Microsoft Corporation. All rights reserved.
    >
    >
    >"Michael Palermiti [MSFT]"

    <michaelp@online.microsoft.com> wrote in message
    >news:%23DxwJ17%23DHA.4072@tk2msftngp13.phx.gbl...
    >> Simon -
    >>
    >> You have not mentioned why you lowered the cache to

    such an extraordinary
    >> low value. You did mention any virtual memory error

    events, like the
    >> 9582's. Please keep in mind that just because the

    Store.exe appears to be
    >> using a lot of physical and virtual memory (working

    set and virtual
    >bytes),
    >> does not mean you should lower the cache to something

    like 262MB. By
    >doing
    >> so, you are putting a lot more pressure on the disk

    subsystem, which in
    >many
    >> cases will lead to other kinds of undesired things...

    for instance, disk
    >> bottlenecks (latecny, etc.). The lowest value I would

    recommend lowering
    >> the cache to would be "147456" (= 576Mb). This is the

    Exchange Product
    >> Group's recommended minimum. It's good to use on

    Windows 2000 Standard
    >> Servers that can not use the /3GB switch and severe VM-

    constrained
    >servers.
    >> Which leads me back to my original thought... you did

    not mention the 9582
    >> Events in the Application Event Viewer Log.
    >>
    >> I would suggest you do not adjust this cache unless

    you need to. I would
    >> recommend you remove the value in AD, so the value

    reads "Not Set",
    >allowing
    >> the Store to use the default size of 858Mb. That

    default cache is mapped
    >in
    >> the virtaul address space, where each process gets 2GB

    of virtual
    >addresses
    >> to use (regardless of how much RAM is installed).

    That VA space can be
    >> increased from 2GB to 3GB by placing the "/3GB" switch

    in the boot.ini
    >> provided: 1] the server has 1GB RAM or more; and 2]

    the OS is at least W2K
    >> Advanced or any version of W2K3.
    >>
    >> In summary, if the Store is generating 9582 events

    then the cache can be
    >> adjusted to combat the problem.
    >>
    >> For more details on the Virtual Memory Fragmentation

    issue and store
    >cache,
    >> please see my most recent weblog entries at the MSDN

    site:
    >> http://blogs.msdn.com/mfp2
    >>
    >> Hope this helps.
    >>
    >> -------------------------
    >> Michael Palermiti
    >> Enterprise Messaging Support
    >>
    >> This posting is provided "AS IS" with no warranties,

    and confers no
    >rights.
    >> © 2004 Microsoft Corporation. All rights reserved.
    >>
    >>
    >> "Simon" <skarrer@nexustechgroup.com> wrote in message
    >> news:148701c3fbb6$90fdd600$a401280a@phx.gbl...
    >> > I have limited the store cache size to 262 MB (See
    >> > Microsoft Knowledge Base Article - 266768 and set the
    >> > msExchESEParamCacheSizeMax = 65536). I restartet the
    >> > server and waited. Now after a few days, the

    store.exe is
    >> > still growing (Taskmanager shows 336 MB). I have an
    >> > Exchangeserver 2000 with SP4. Can anybody help me?
    >> >
    >> > Thanks
    >> >

    >>
    >>

    >
    >
    >.
    >


+ Reply to Thread

Similar Threads

  1. Efficient way to store a limited number of booleans
    By Application Development in forum c++
    Replies: 11
    Last Post: 12-12-2007, 09:24 AM
  2. Re: growing case structures
    By Application Development in forum labview
    Replies: 0
    Last Post: 09-19-2007, 03:10 PM
  3. Help! Why is my database growing?
    By Application Development in forum Inetserver
    Replies: 1
    Last Post: 12-15-2005, 05:32 PM
  4. Private store is growing
    By Application Development in forum Microsoft Exchange
    Replies: 0
    Last Post: 08-09-2004, 11:21 AM
  5. Store.exe growing exponentially/quickly! Crash server!!
    By Application Development in forum Microsoft Exchange
    Replies: 2
    Last Post: 02-14-2004, 12:51 AM