Store.exe eating up lots of RAM (around 1GB)

Hello,

W2k server running Exchange 2000. Store.exe has been consuming up to 1GB of
RAM (out of 2GB total), and appears to be slowing the server down. I don't
recall Store.exe ever consuming that much RAM before and it seems to have
started this past 7 days or so. If I stop and restart the service or reboot
the server, it goes back down to about 70MB usage and 1.2GB free RAM. It can
run all day like this, then when I come in the next morning the memory usage
spikes again. Is store.exe supposed to consume this much RAM?

I've done searches online and read things ranging from it's normal for
store.exe to consume as much RAM as possible (on Exchange 5.5 though), to
problems occurring when trying to run tape backups during the default time of
mailbox store maintenance of 1am-5am. I'm not real sure what to believe
becuase as I said this seems to have just started this past week. I ran a
full virus scan on the server and didn't find anything. Microsoft has
articles on CPU consumption being up to 100% with store.exe, but that was
with Exchange 5.5 again and our actual CPU usage is normally under 10.

Thanks for any help!

MN4runner

Yes, this is normal for the store.exe to consume this much memory. Exchange
uses something called Dynamic Buffer Allocation to use as much physical
memory as it can, and release some when the OS (or other apps) request it. I
don't recall if there is a percentage of totaly memory that it uses or not
off hand.

"mn4runner" <mn4runner@discussions.microsoft.com> wrote in message
news:BCD57EB4-6451-4EA9-8B9A-C0EDAAA7623C@microsoft.com...
> Hello,
>
> W2k server running Exchange 2000. Store.exe has been consuming up to 1GB
> of
> RAM (out of 2GB total), and appears to be slowing the server down. I
> don't
> recall Store.exe ever consuming that much RAM before and it seems to have
> started this past 7 days or so. If I stop and restart the service or
> reboot
> the server, it goes back down to about 70MB usage and 1.2GB free RAM. It
> can
> run all day like this, then when I come in the next morning the memory
> usage
> spikes again. Is store.exe supposed to consume this much RAM?
>
> I've done searches online and read things ranging from it's normal for
> store.exe to consume as much RAM as possible (on Exchange 5.5 though), to
> problems occurring when trying to run tape backups during the default time
> of
> mailbox store maintenance of 1am-5am. I'm not real sure what to believe
> becuase as I said this seems to have just started this past week. I ran a
> full virus scan on the server and didn't find anything. Microsoft has
> articles on CPU consumption being up to 100% with store.exe, but that was
> with Exchange 5.5 again and our actual CPU usage is normally under 10.
>
> Thanks for any help!
>
> MN4runner

Thanks for the reply. I could only find info on Exchange 5.5 and store.exe
taking up as much RAM as it could. I couldn't find anything about Exchange
2000.

I apologize for the triple posts. After clicking on the post button, twice
I got an error message saying there was an internal error on the website and
that my post did not make it. So I tried 3 times before it finally worked.
It apparently worked all three times!

Thanks,

ShawnF

"Gabe Matteson" wrote:

> Yes, this is normal for the store.exe to consume this much memory. Exchange
> uses something called Dynamic Buffer Allocation to use as much physical
> memory as it can, and release some when the OS (or other apps) request it. I
> don't recall if there is a percentage of totaly memory that it uses or not
> off hand.
>
> "mn4runner" <mn4runner@discussions.microsoft.com> wrote in message
> news:BCD57EB4-6451-4EA9-8B9A-C0EDAAA7623C@microsoft.com...
> > Hello,
> >
> > W2k server running Exchange 2000. Store.exe has been consuming up to 1GB
> > of
> > RAM (out of 2GB total), and appears to be slowing the server down. I
> > don't
> > recall Store.exe ever consuming that much RAM before and it seems to have
> > started this past 7 days or so. If I stop and restart the service or
> > reboot
> > the server, it goes back down to about 70MB usage and 1.2GB free RAM. It
> > can
> > run all day like this, then when I come in the next morning the memory
> > usage
> > spikes again. Is store.exe supposed to consume this much RAM?
> >
> > I've done searches online and read things ranging from it's normal for
> > store.exe to consume as much RAM as possible (on Exchange 5.5 though), to
> > problems occurring when trying to run tape backups during the default time
> > of
> > mailbox store maintenance of 1am-5am. I'm not real sure what to believe
> > becuase as I said this seems to have just started this past week. I ran a
> > full virus scan on the server and didn't find anything. Microsoft has
> > articles on CPU consumption being up to 100% with store.exe, but that was
> > with Exchange 5.5 again and our actual CPU usage is normally under 10.
> >
> > Thanks for any help!
> >
> > MN4runner
>
>
>

It's the same for Exchange 2000 and Exchange 2003. SQL also uses DBA, too.

--
Neil Hobson
Exchange MVP

For Exchange news, links and tips, check:
http://www.msexchangeblog.com

"mn4runner" <mn4runner@discussions.microsoft.com> wrote in message
news:C4F090ED-D015-4C68-A2B9-9DB918EDE0FC@microsoft.com...
> Thanks for the reply. I could only find info on Exchange 5.5 and store.exe
> taking up as much RAM as it could. I couldn't find anything about
Exchange
> 2000.
>
> I apologize for the triple posts. After clicking on the post button,
twice
> I got an error message saying there was an internal error on the website
and
> that my post did not make it. So I tried 3 times before it finally
worked.
> It apparently worked all three times!
>
> Thanks,
>
> ShawnF
>
> "Gabe Matteson" wrote:
>
> > Yes, this is normal for the store.exe to consume this much memory.
Exchange
> > uses something called Dynamic Buffer Allocation to use as much physical
> > memory as it can, and release some when the OS (or other apps) request
it. I
> > don't recall if there is a percentage of totaly memory that it uses or
not
> > off hand.
> >
> > "mn4runner" <mn4runner@discussions.microsoft.com> wrote in message
> > news:BCD57EB4-6451-4EA9-8B9A-C0EDAAA7623C@microsoft.com...
> > > Hello,
> > >
> > > W2k server running Exchange 2000. Store.exe has been consuming up to
1GB
> > > of
> > > RAM (out of 2GB total), and appears to be slowing the server down. I
> > > don't
> > > recall Store.exe ever consuming that much RAM before and it seems to
have
> > > started this past 7 days or so. If I stop and restart the service or
> > > reboot
> > > the server, it goes back down to about 70MB usage and 1.2GB free RAM.
It
> > > can
> > > run all day like this, then when I come in the next morning the memory
> > > usage
> > > spikes again. Is store.exe supposed to consume this much RAM?
> > >
> > > I've done searches online and read things ranging from it's normal for
> > > store.exe to consume as much RAM as possible (on Exchange 5.5 though),
to
> > > problems occurring when trying to run tape backups during the default
time
> > > of
> > > mailbox store maintenance of 1am-5am. I'm not real sure what to
believe
> > > becuase as I said this seems to have just started this past week. I
ran a
> > > full virus scan on the server and didn't find anything. Microsoft has
> > > articles on CPU consumption being up to 100% with store.exe, but that
was
> > > with Exchange 5.5 again and our actual CPU usage is normally under 10.
> > >
> > > Thanks for any help!
> > >
> > > MN4runner
> >
> >
> >

welcome

"mn4runner" <mn4runner@discussions.microsoft.com> wrote in message
news:BCD57EB4-6451-4EA9-8B9A-C0EDAAA7623C@microsoft.com...
> Hello,
>
> W2k server running Exchange 2000. Store.exe has been consuming up to 1GB
> of
> RAM (out of 2GB total), and appears to be slowing the server down. I
> don't
> recall Store.exe ever consuming that much RAM before and it seems to have
> started this past 7 days or so. If I stop and restart the service or
> reboot
> the server, it goes back down to about 70MB usage and 1.2GB free RAM. It
> can
> run all day like this, then when I come in the next morning the memory
> usage
> spikes again. Is store.exe supposed to consume this much RAM?
>
> I've done searches online and read things ranging from it's normal for
> store.exe to consume as much RAM as possible (on Exchange 5.5 though), to
> problems occurring when trying to run tape backups during the default time
> of
> mailbox store maintenance of 1am-5am. I'm not real sure what to believe
> becuase as I said this seems to have just started this past week. I ran a
> full virus scan on the server and didn't find anything. Microsoft has
> articles on CPU consumption being up to 100% with store.exe, but that was
> with Exchange 5.5 again and our actual CPU usage is normally under 10.
>
> Thanks for any help!
>
> MN4runner

The algorithm improved significantly for Exchange 2003. Prior to that
there were problems if the system cache was large (which can happen if
you also use the Exchange Server as a file server).

There are ways to set upper and lower limits for the database cache. I
don't know off hand what they are, because I'm only familiar with how
store.exe sets it, not how admins tell the store what to use.

SQL does NOT use DBA. They listen for 'high' or 'low' memory signals
from the OS to size their cache. Only ESE and ESENT use DBA. (ESENT is
used by Active Directory, and some other OS components).

-martin

Boring-but-necessary-disclaimer: This posting is provided "AS IS" with
no warranties, and confers no rights.


In article <erP1JYgsEHA.1452@TK2MSFTNGP11.phx.gbl>,
Neil Hobson [MVP] <neil.hobson@nospam.silversands.co.uk> wrote:
>It's the same for Exchange 2000 and Exchange 2003. SQL also uses DBA, too.
>
>--
>Neil Hobson
>Exchange MVP
>
>For Exchange news, links and tips, check:
>http://www.msexchangeblog.com
>
>"mn4runner" <mn4runner@discussions.microsoft.com> wrote in message
>news:C4F090ED-D015-4C68-A2B9-9DB918EDE0FC@microsoft.com...
>> Thanks for the reply. I could only find info on Exchange 5.5 and store.exe
>> taking up as much RAM as it could. I couldn't find anything about
>Exchange
>> 2000.
>>
>> I apologize for the triple posts. After clicking on the post button,
>twice
>> I got an error message saying there was an internal error on the website
>and
>> that my post did not make it. So I tried 3 times before it finally
>worked.
>> It apparently worked all three times!
>>
>> Thanks,
>>
>> ShawnF
>>
>> "Gabe Matteson" wrote:
>>
>> > Yes, this is normal for the store.exe to consume this much memory.
>Exchange
>> > uses something called Dynamic Buffer Allocation to use as much physical
>> > memory as it can, and release some when the OS (or other apps) request
>it. I
>> > don't recall if there is a percentage of totaly memory that it uses or
>not
>> > off hand.
>> >
>> > "mn4runner" <mn4runner@discussions.microsoft.com> wrote in message
>> > news:BCD57EB4-6451-4EA9-8B9A-C0EDAAA7623C@microsoft.com...
>> > > Hello,
>> > >
>> > > W2k server running Exchange 2000. Store.exe has been consuming up to
>1GB
>> > > of
>> > > RAM (out of 2GB total), and appears to be slowing the server down. I
>> > > don't
>> > > recall Store.exe ever consuming that much RAM before and it seems to
>have
>> > > started this past 7 days or so. If I stop and restart the service or
>> > > reboot
>> > > the server, it goes back down to about 70MB usage and 1.2GB free RAM.
>It
>> > > can
>> > > run all day like this, then when I come in the next morning the memory
>> > > usage
>> > > spikes again. Is store.exe supposed to consume this much RAM?
>> > >
>> > > I've done searches online and read things ranging from it's normal for
>> > > store.exe to consume as much RAM as possible (on Exchange 5.5 though),
>to
>> > > problems occurring when trying to run tape backups during the default
>time
>> > > of
>> > > mailbox store maintenance of 1am-5am. I'm not real sure what to
>believe
>> > > becuase as I said this seems to have just started this past week. I
>ran a
>> > > full virus scan on the server and didn't find anything. Microsoft has
>> > > articles on CPU consumption being up to 100% with store.exe, but that
>was
>> > > with Exchange 5.5 again and our actual CPU usage is normally under 10.
>> > >
>> > > Thanks for any help!
>> > >
>> > > MN4runner
>> >
>> >
>> >
>
>

Ah, ok, cheers for that Martin. I'm not a SQL guy (you'd never guess!) so I
just lumped it under the 'grab memory' category!

--
Neil Hobson
Exchange MVP

For Exchange news, links and tips, check:
http://www.msexchangeblog.com

"Martin Chisholm [MSFT]" <martinc@online.microsoft.com> wrote in message
news:ckmig6$15f$1@drizzle.com...
> The algorithm improved significantly for Exchange 2003. Prior to that
> there were problems if the system cache was large (which can happen if
> you also use the Exchange Server as a file server).
>
> There are ways to set upper and lower limits for the database cache. I
> don't know off hand what they are, because I'm only familiar with how
> store.exe sets it, not how admins tell the store what to use.
>
> SQL does NOT use DBA. They listen for 'high' or 'low' memory signals
> from the OS to size their cache. Only ESE and ESENT use DBA. (ESENT is
> used by Active Directory, and some other OS components).
>
> -martin
>
> Boring-but-necessary-disclaimer: This posting is provided "AS IS" with
> no warranties, and confers no rights.
>
>
> In article <erP1JYgsEHA.1452@TK2MSFTNGP11.phx.gbl>,
> Neil Hobson [MVP] <neil.hobson@nospam.silversands.co.uk> wrote:
> >It's the same for Exchange 2000 and Exchange 2003. SQL also uses DBA,
too.
> >
> >--
> >Neil Hobson
> >Exchange MVP
> >
> >For Exchange news, links and tips, check:
> >http://www.msexchangeblog.com
> >
> >"mn4runner" <mn4runner@discussions.microsoft.com> wrote in message
> >news:C4F090ED-D015-4C68-A2B9-9DB918EDE0FC@microsoft.com...
> >> Thanks for the reply. I could only find info on Exchange 5.5 and
store.exe
> >> taking up as much RAM as it could. I couldn't find anything about
> >Exchange
> >> 2000.
> >>
> >> I apologize for the triple posts. After clicking on the post button,
> >twice
> >> I got an error message saying there was an internal error on the
website
> >and
> >> that my post did not make it. So I tried 3 times before it finally
> >worked.
> >> It apparently worked all three times!
> >>
> >> Thanks,
> >>
> >> ShawnF
> >>
> >> "Gabe Matteson" wrote:
> >>
> >> > Yes, this is normal for the store.exe to consume this much memory.
> >Exchange
> >> > uses something called Dynamic Buffer Allocation to use as much
physical
> >> > memory as it can, and release some when the OS (or other apps)
request
> >it. I
> >> > don't recall if there is a percentage of totaly memory that it uses
or
> >not
> >> > off hand.
> >> >
> >> > "mn4runner" <mn4runner@discussions.microsoft.com> wrote in message
> >> > news:BCD57EB4-6451-4EA9-8B9A-C0EDAAA7623C@microsoft.com...
> >> > > Hello,
> >> > >
> >> > > W2k server running Exchange 2000. Store.exe has been consuming up
to
> >1GB
> >> > > of
> >> > > RAM (out of 2GB total), and appears to be slowing the server down.
I
> >> > > don't
> >> > > recall Store.exe ever consuming that much RAM before and it seems
to
> >have
> >> > > started this past 7 days or so. If I stop and restart the service
or
> >> > > reboot
> >> > > the server, it goes back down to about 70MB usage and 1.2GB free
RAM.
> >It
> >> > > can
> >> > > run all day like this, then when I come in the next morning the
memory
> >> > > usage
> >> > > spikes again. Is store.exe supposed to consume this much RAM?
> >> > >
> >> > > I've done searches online and read things ranging from it's normal
for
> >> > > store.exe to consume as much RAM as possible (on Exchange 5.5
though),
> >to
> >> > > problems occurring when trying to run tape backups during the
default
> >time
> >> > > of
> >> > > mailbox store maintenance of 1am-5am. I'm not real sure what to
> >believe
> >> > > becuase as I said this seems to have just started this past week.
I
> >ran a
> >> > > full virus scan on the server and didn't find anything. Microsoft
has
> >> > > articles on CPU consumption being up to 100% with store.exe, but
that
> >was
> >> > > with Exchange 5.5 again and our actual CPU usage is normally under
10.
> >> > >
> >> > > Thanks for any help!
> >> > >
> >> > > MN4runner
> >> >
> >> >
> >> >
> >
> >
>
>