Re: Indexing uses *lots* of memory
- From: "David Beaven" <idstechnet@xxxxxxxxxxxxxxx>
- Date: Fri, 17 Nov 2006 09:30:04 -0000
Chace
Thanks for your reply. I'm not worried about store.exe memory usage (the
server supports over 500 users). It is the memory usage related to indexing
and the fact that 1.2gb wasn't reported in task manager. Have you any
specifics on what counters (perfmon) to trace to find this missing memory
usage?
Thanks
David
"chace zhang" <v-chacez@xxxxxxxxxxxxx> wrote in message
news:KaBdaKiCHHA.268@xxxxxxxxxxxxxxxxxxxxxxxx
Hi,
Thank you for posting here.
In general, STORE.exe will use as much memory as is available on the
server, but will release the memory when other processes/applications need
it. However, the "store.exe"-related processes like virus scanning may
cause the memory usage increasing unexpectedly. For more Information about
Exchange and Antivirus software, please refer to the following Microsoft
Knowledge Base article:
328841 XADM: Exchange and Antivirus Software
http://support.microsoft.com/?id=328841
Another cause to the unexpected high memory usage of the Store.exe process
is that the AV or backup program scan the MDBDATA folder and drive M:. You
may need to make sure that the MDBDATA folder and drive M: have been
excluded from their scan lists.
298924 XADM: Do Not Back Up or Scan Exchange 2000 Drive M
http://support.microsoft.com/?id=298924
If this issue persists after that, please check the related information
that will help us to get more ideas on this behavior:
========
1. System Monitor logs (also known as Performance Monitor logs).
NOTE: If this issue can disappear after we restart the server, please keep
the monitor running since restart and stop the monitor when this issue
recurs.
2. Event logs
3. System Information file (WINMSD)
NOTE: To collect information, please refer to the following
Microsoft Knowledge Base article:
317411 XADM: How to Gather Data to Troubleshoot Exchange Virtual Memory
Issues
http://support.microsoft.com/?id=317411
Please let me know the results so that I can provide further assistance on
this problem. I am looking forward to your reply. Thanks and have a nice
day!
Best Regards,
Chace Zhang (MSFT)
Microsoft CSS Online Newsgroup Support
Get Secure! - www.microsoft.com/security
=====================================================
This newsgroup only focuses on Exchange technical issues. If you have
issues regarding other Microsoft products, you'd better post in the
corresponding newsgroups so that they can be resolved in an efficient and
timely manner. You can locate the newsgroup here:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx
When opening a new thread via the web interface, we recommend you check
the
"Notify me of replies" box to receive e-mail notifications when there are
any updates in your thread. When responding to posts via your newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.
Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In
doing
so, it will ensure your issues are resolved in a timely manner.
For urgent issues, you may want to contact Microsoft CSS directly. Please
check http://support.microsoft.com for regional support phone numbers.
Any input or comments in this thread are highly appreciated.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no
rights.
--------------------
| From: "David Beaven" <idstechnet@xxxxxxxxxxxxxxx>
| Subject: Indexing uses *lots* of memory
| Date: Thu, 16 Nov 2006 15:12:41 -0000
| Lines: 20
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2900.2869
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962
| X-RFC2646: Format=Flowed; Original
| Message-ID: <eWycgGZCHHA.468@xxxxxxxxxxxxxxxxxxxx>
| Newsgroups: microsoft.public.exchange2000.general
| NNTP-Posting-Host: cats1945.ids.ac.uk 139.184.194.214
| Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP06.phx.gbl
| Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.exchange2000.general:71284
| X-Tomcat-NG: microsoft.public.exchange2000.general
|
| On our exchange 2000 server (latest SP etc) the index service is setup
and
| on a server with 3gb memory we have:
| store.exe 1.1gb
| mssearch 200MB
| mssdmn.exe 200MB
| and a total commit charge of 3.5gb
|
| On stopping the mssearch service we lose mssearch.exe quickly - there is
| then a lengthy pause and then mssdmn.exe exits and the commit charge
| plummits to 1.9gb - so indexing was using 1.6gb memory - most of it
| unreported in task manager. Is there a way to limit memory usage of
| indexing (to avoid excessive paging) or is this a memory leak. Closest
I
| could find to this (but no help) was:
|
| http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q308797
|
| Thanks
| David
|
|
|
.
- Follow-Ups:
- Re: Indexing uses *lots* of memory
- From: chace zhang
- Re: Indexing uses *lots* of memory
- References:
- Indexing uses *lots* of memory
- From: David Beaven
- RE: Indexing uses *lots* of memory
- From: chace zhang
- Indexing uses *lots* of memory
- Prev by Date: RE: Indexing uses *lots* of memory
- Next by Date: Unknown emails
- Previous by thread: RE: Indexing uses *lots* of memory
- Next by thread: Re: Indexing uses *lots* of memory
- Index(es):
Relevant Pages
|
|