Re: Allocated Memory alerts
- From: v-yanniw@xxxxxxxxxxxxxxxxxxxx ("Jenny wu [MSFT]")
- Date: Fri, 23 Jun 2006 06:17:11 GMT
Hi Dima,
Thanks for using the SBS newsgroup. Many thanks for Tim's input.
From your description, I understand that you received the memory allocationalerts such as "A large amount of memory is committed to applications and
processes" and "The inetinfo.exe process is allocating more memory than
usual" on the SBS server box. If I am off base, please don't hesitate to
let me know.
If you do not encounter any real server performance issue, I think at least
this server is fine regardless these warnings. Then, let's focus on these
warnings and let me introduce you with more information on it.
Generally speaking, since the SBS 2003 server is an integrated solution
including multiple services such as Exchange, IIS, SQL, ISA, Windows
infrastructure etc, the high memory usage is expected. However, different
servers will have different stories.
The Health monitor is running on the SBS server. The alert feature is
provided by Health monitor component. Open Health Monitor console in
Administrative Tools, navigate to All Monitored Computers\ServerName\Small
Business Server Alerts\Core Server Alerts\, you will find an object named
'Allocated Memory'. This predefined object monitors the committed bytes of
the SBS server and sends the alert when the value reaches the threshold.
The value is approximate to the "Total Commit Charge" value in Task
Manager.
A memory allocation threshold is configured on the particular monitored
object. When the average value of the object (for example, the committed
memory size) reaches the threshold, the server will send an alert e-mail to
the admin to check if the server encounters performance issue. It just a
reminder and do not control the memory allocation for specific process. For
the memory allocation size, the default threshold is 2147483648.
This memory allocation value is depending on the current server load,
physical memory size and page file size on the SBS server. For a SBS server
with large physical memory (for example 2GB), it's expected that the
committed bytes is high. The committed bytes counter indicates the Memory
allocated to programs and the operating system. Technically speaking, some
processes such as Exchange store process and SQL database engine could use
as much memory as they can. This causes high memory usage behavior on a SBS
server.
The counter that is being triggered in Health Monitor is for Allocated
Memory > 2,147,483,648 bytes; this number is static and is configured
similarly on all SBS 2003 server installations, this might mean that that
number may not be representing the true baseline for that particular server
installation. If you can confirm that everything is working as expected,
that there are no problems/errors with the system, then you can actually
check the average count and change it to match that system.
You can do it from the Monitoring and Reporting snap-in in Server
Management (under Change Alert Notifications, then select Performance
Counters, and then check the Counter Average for Allocated Memory. You can
then Edit that entry and replace the default threshold with the average for
that system (plus some padding)).
I. The best way to identify the memory threshold on a particular SBS server
is to use the performance monitor utility. We can use the utility to
capture a long term memory and process status (5 to 10 days) and then
analyze the performance log to get the average memory usage of the SBS
server. Then, we can define the memory allocation threshold of the SBS
server. Generally speaking, we can use the 130%~ 140% average values as the
threshold.
To do so, open Server Management console, navigate to 'Monitoring and
Reporting'. Click 'Change Alert Notifications'. In 'Performance Counters'
tab, double-click 'Inetinfo.exe private bytes inetinfo'. Change the
threshold from 104857600 to 188583269 (140%*Current average value).
II. In addition, please make sure that you have already applied the
integration patch for Exchange 2003 SP1. Otherwise, you could receive
memory alert of store.exe process:
http://www.microsoft.com/downloads/details.aspx?FamilyId=0FE89C95-E767-428C-
8621-6A586C655EE3&displaylang=en
III. Have you edited the Boot.ini file to optimize the virtual memory usage
of the Information Store service? You can do as steps below to make sure
that Exchange Server 2003 can make efficient use of that memory.
- Add the /3GB switch to the Boot.ini file on the server.
- Set the /USERVA=3030 parameter in the Boot.ini file.
- Configure the HeapDeCommitFreeBlockThreshold registry value in the
following registry key, and then restart the server:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager
Value name: HeapDeCommitFreeBlockThreshold
Value type: REG_DWORD
Value data: 0x00040000 (recommended)
Value default: not present
You may also increase the number of messages Exchange can send at one time.
Related information:
316739 How to Use the /USERVA Switch in the Boot.ini File to Tune /3GB
Configurations
http://support.microsoft.com/?id=316739
810371 XADM: Using the /Userva Switch on Windows Server 2003-Based Exchange
Servers
http://support.microsoft.com/?id=810371
823440 You Must Use the /3GB Switch When You Install Exchange Server 2003
on a Windows Server 2003-Based System
http://support.microsoft.com/?id=823440
815372 How to Optimize Memory Usage in Exchange Server 2003
http://support.microsoft.com/?id=815372
IV. To the sqlservr.exe process memory allocation, you can use the
following method to control:
(1). Firstly, we need to use the steps below to identify what instance is
using the most memory: In Task Manager, click Select Columns in the View
menu, and make sure that PID (Process Identifier) is checked. Then find out
the sqlservr.exe process that is using the most of the RAM and note its
PID. Once you have the PID run the following from a command prompt:
tasklist /svc
This should give you the instance associated with the PID you identified in
the previous step. And then you can configure a maximum amount of memory to
the instance.
(2). Then, use max server memory to prevent SQL Server from using more that
the specified amount of memory (we can also use min server memory to
guarantee a minimum amount of memory to an instance of SQL Server). To do
so, open a command prompt and run the following command:
osql -E -S <SBS server name>\<instance name>
You will enter the osql command prompt. Run the commends below (replace
<xxx> with the maximum and minimum amount of memory respectively):
1> EXEC sp_configure 'show advanced options', 1
2> reconfigure
3> go
1> EXEC sp_configure 'min server memory', <xxx>
2> reconfigure
3> go
1> EXEC sp_configure 'max server memory', <xxx>
2> reconfigure
3> go
After doing the above steps, you may run the commands to check the
configured memory usage:
1> EXEC sp_configure
2> go
Hope above information helps. If you have further question on the issue,
please let me know. I am happy to be of assistance to you and look forward
to your reply.
Have a nice day!
Sincerely,
Jenny Wu
Microsoft CSS Online Newsgroup Support
Get Secure! - www.microsoft.com/security
======================================================
This newsgroup only focuses on SBS 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: timbarrett@xxxxxxxxxxxxxxxxxxxx (Tim Barrett)5.1.2600.0; http://www.rssbandit.org)
X-Newsreader: RssBandit/1.3.0.42 (.NET CLR 1.1.4322.2032; WinNT
Subject: Re: Allocated Memory alertsExchange store.
References: <B0E5C967-3426-4834-9157-957FE2D6B307@xxxxxxxxxxxxx>
Message-ID: <uMVvN0hlGHA.3740@xxxxxxxxxxxxxxxxxxxx>
Newsgroups: microsoft.public.windows.server.sbs
Date: Thu, 22 Jun 2006 09:58:13 -0700
NNTP-Posting-Host: 216-107-103-4.wan.networktel.net 216.107.103.4
Lines: 1
Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP02.phx.gbl
Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.sbs:276785
X-Tomcat-NG: microsoft.public.windows.server.sbs
Dima,
Have you recently added more physical RAM to either of these SBS servers?
If so, scroll down to the June 20 post 'Memory Alert'.
If you haven't added more RAM, make sure that your A/V is not scanning the
hread/thread/ab2b40555a90cefe/fb1797d1f72a2654?lnk=st&q=The+inetinfo.exe+pro
You can also check out this pose:
http://groups.google.com/group/microsoft.public.windows.server.sbs/browse_t
cess+is+allocating+more+memory+than+usual&rnum=2&hl=en#fb1797d1f72a2654
-Tim Barrett
Microsoft Certified Professional
Microsoft Small Business Specialist
Website: http://www.NoGeekLeftBehind.com
.
- References:
- Re: Allocated Memory alerts
- From: Tim Barrett
- Re: Allocated Memory alerts
- Prev by Date: RE: ISA Server Management console fails to load
- Next by Date: RE: SBS Folder Redirection
- Previous by thread: Re: Allocated Memory alerts
- Next by thread: Re: Allocated Memory alerts
- Index(es):
Relevant Pages
|
