Excessive Page Faults?

I am noticing that an many of my servers (Server 2003 EE SP2 R2), that the
MsMpEng.exe and MOMHost.exe processes are creating a significant number of
page faults.
For example, on my SQL 2000 SP4 server with 4GB RAM which has been up for 19
days has nearly 19M page faults on MsMpEng and over 16M faults on MOMHost.
Another example is my Exchange 2003 SP2 with 4GB RAM which has also been up
for 19 days has nearly 182M faults on MsMpEng and nearly 16M faults on
MOMHost.
Keep in mind that the "M" with the number is million.
We only recently started using Forefront on our servers, and this appears to
be a relatively new issue, and I would like to know if others have been
experiencing this as well.
RichardThis is not an exchange issue...
But take a look at
http://geekswithblogs.net/Coleman/archive/2007/03/26/109906.aspx
"Richard Perry" <RichardPerry@.newsgroup.nospam> wrote in message
news:3BFD2358-2798-4A29-B54A-EA90AD883293@.microsoft.com...
>I am noticing that an many of my servers (Server 2003 EE SP2 R2), that the
>MsMpEng.exe and MOMHost.exe processes are creating a significant number of
>page faults.
> For example, on my SQL 2000 SP4 server with 4GB RAM which has been up for
> 19 days has nearly 19M page faults on MsMpEng and over 16M faults on
> MOMHost.
> Another example is my Exchange 2003 SP2 with 4GB RAM which has also been
> up for 19 days has nearly 182M faults on MsMpEng and nearly 16M faults on
> MOMHost.
> Keep in mind that the "M" with the number is million.
> We only recently started using Forefront on our servers, and this appears
> to be a relatively new issue, and I would like to know if others have been
> experiencing this as well.
> Richard|||Thanks for the link to the article. This does give some additional
information, however the problem in the article points more to high CPU
utilization rather than high number of page faults. Perhaps since this also
includes the MOM components, I should try posting in that forum as the
Forefront group is fairly new?
Richard
"Betelgeuse" <betelgeuse@.news.postalias> wrote in message
news:OBAYHbCDIHA.3712@.TK2MSFTNGP02.phx.gbl...
> This is not an exchange issue...
> But take a look at
> http://geekswithblogs.net/Coleman/archive/2007/03/26/109906.aspx
>
> "Richard Perry" <RichardPerry@.newsgroup.nospam> wrote in message
> news:3BFD2358-2798-4A29-B54A-EA90AD883293@.microsoft.com...
>>I am noticing that an many of my servers (Server 2003 EE SP2 R2), that the
>>MsMpEng.exe and MOMHost.exe processes are creating a significant number of
>>page faults.
>> For example, on my SQL 2000 SP4 server with 4GB RAM which has been up for
>> 19 days has nearly 19M page faults on MsMpEng and over 16M faults on
>> MOMHost.
>> Another example is my Exchange 2003 SP2 with 4GB RAM which has also been
>> up for 19 days has nearly 182M faults on MsMpEng and nearly 16M faults on
>> MOMHost.
>> Keep in mind that the "M" with the number is million.
>> We only recently started using Forefront on our servers, and this appears
>> to be a relatively new issue, and I would like to know if others have
>> been experiencing this as well.
>> Richard
>|||Dear Richard,
Thank you for posting here.
I understand that the process MsMpEng.exe and MOMHost.exe processes are
creating a significant number of page faults on several servers.
According to your description, it appears that the issue should not on the
SQL Server side. Based on my experience, this behavior can occur due to a
Memory Leak but sometimes it is normal for some processes. In order to
ensure the current status, I would like to confirm the following
information before going further:
1. Has the performance on these severs been affected due to this issue?
2. Please also use the Performance Monitor utility to monitor the stability
of memory pages used by these two processes.
To do so, please refer to the following steps:
--
a. Enter the Control Panel -> Administrative Tools -> Performance.
b. Select "Process" in the "Performance object" selection
c. Add the following counter for the two processes (MsMpEng.exe and
MOMHost.exe) in question:
- Working Set (The Working Set is the set of memory pages touched recently
by the threads in the process)
- Virtual Bytes (Virtual Bytes is the current size, in bytes, of the
virtual address space the process is using)
NOTE: You can also add some main process for this server. E.X: sqlservr.exe
process
d. If the indication goes very smoothly, it indicates that the memory usage
of these processes is stable. In opposition, the memory leak issue may
exist.
At the same time, on the SQL Server side, we can attempt to adjust the
memory to see if it helps. Below are the detail steps:
--
a. Open the SQL Server Management Studio
b. Right click on the SQL Server instance->choose Properties.
c. Click on the Memory tab on the left panel, adjust the memory for your
SQL Server.
Have a nice day!
Best regards,
Adams Qu
MCSE, MCDBA, MCTS
Microsoft Online Support
Microsoft Global Technical Support Center
Get Secure! - www.microsoft.com/security
=====================================================When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.
--
| From: "Richard Perry" <RichardPerry@.newsgroup.nospam>
| References: <3BFD2358-2798-4A29-B54A-EA90AD883293@.microsoft.com>
<OBAYHbCDIHA.3712@.TK2MSFTNGP02.phx.gbl>
| Subject: Re: Excessive Page Faults?
| Date: Thu, 11 Oct 2007 12:56:40 -0700
| Lines: 1
| Message-ID: <84D91F2A-E4A6-4933-B34B-72879DD28277@.microsoft.com>
| MIME-Version: 1.0
| Content-Type: text/plain;
| format=flowed;
| charset="iso-8859-1";
| reply-type=response
| Content-Transfer-Encoding: 7bit
| X-Priority: 3
| X-MSMail-Priority: Normal
| Importance: Normal
| X-Newsreader: Microsoft Windows Live Mail 12.0.1365
| X-MimeOLE: Produced By Microsoft MimeOLE V12.0.1365
| X-MS-CommunityGroup-PostID: {84D91F2A-E4A6-4933-B34B-72879DD28277}
| X-MS-CommunityGroup-ThreadID: 3BFD2358-2798-4A29-B54A-EA90AD883293
| X-MS-CommunityGroup-ParentID: 47993B93-4F51-47EE-BE41-7DBD1C4B8AF7
| Newsgroups:
microsoft.public.exchange.admin,microsoft.public.security.forefront,microsof
t.public.sqlserver.server
| Path: TK2MSFTNGHUB02.phx.gbl
| Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.security.forefront:71
microsoft.public.sqlserver.server:27713
microsoft.public.exchange.admin:47476
| NNTP-Posting-Host: TK2MSFTNGHUB02.phx.gbl 127.0.0.1
| X-Tomcat-NG: microsoft.public.sqlserver.server
|
| Thanks for the link to the article. This does give some additional
| information, however the problem in the article points more to high CPU
| utilization rather than high number of page faults. Perhaps since this
also
| includes the MOM components, I should try posting in that forum as the
| Forefront group is fairly new?
|
| Richard
|
| "Betelgeuse" <betelgeuse@.news.postalias> wrote in message
| news:OBAYHbCDIHA.3712@.TK2MSFTNGP02.phx.gbl...
| > This is not an exchange issue...
| >
| > But take a look at
| > http://geekswithblogs.net/Coleman/archive/2007/03/26/109906.aspx
| >
| >
| > "Richard Perry" <RichardPerry@.newsgroup.nospam> wrote in message
| > news:3BFD2358-2798-4A29-B54A-EA90AD883293@.microsoft.com...
| >>I am noticing that an many of my servers (Server 2003 EE SP2 R2), that
the
| >>MsMpEng.exe and MOMHost.exe processes are creating a significant number
of
| >>page faults.
| >>
| >> For example, on my SQL 2000 SP4 server with 4GB RAM which has been up
for
| >> 19 days has nearly 19M page faults on MsMpEng and over 16M faults on
| >> MOMHost.
| >>
| >> Another example is my Exchange 2003 SP2 with 4GB RAM which has also
been
| >> up for 19 days has nearly 182M faults on MsMpEng and nearly 16M faults
on
| >> MOMHost.
| >>
| >> Keep in mind that the "M" with the number is million.
| >>
| >> We only recently started using Forefront on our servers, and this
appears
| >> to be a relatively new issue, and I would like to know if others have
| >> been experiencing this as well.
| >>
| >> Richard
| >
| >
||||Dear Richard,
We just want to say hi and check if there is anything further we can do for
you. If there is, please don't hesitate to let us know.
Regards,
Sophie Tan, MCSE 2000
Microsoft Online Support
Microsoft Global Technical Support Center
Get Secure! - www.microsoft.com/security
====================================================When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
====================================================This posting is provided "AS IS" with no warranties, and confers no rights.
| X-Tomcat-ID: 94083421
| References: <3BFD2358-2798-4A29-B54A-EA90AD883293@.microsoft.com>
<OBAYHbCDIHA.3712@.TK2MSFTNGP02.phx.gbl>
<84D91F2A-E4A6-4933-B34B-72879DD28277@.microsoft.com>
| MIME-Version: 1.0
| Content-Type: text/plain
| Content-Transfer-Encoding: 7bit
| From: v-adamqu@.online.microsoft.com (Adams Qu [MSFT])
| Organization: Microsoft
| Date: Fri, 12 Oct 2007 07:35:19 GMT
| Subject: Re: Excessive Page Faults?
| X-Tomcat-NG: microsoft.public.sqlserver.server
| Message-ID: <8LjAyJKDIHA.4664@.TK2MSFTNGHUB02.phx.gbl>
| Newsgroups: microsoft.public.sqlserver.server
| Lines: 132
| Path: TK2MSFTNGHUB02.phx.gbl
| Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.sqlserver.server:27758
| NNTP-Posting-Host: tomcatimport2.phx.gbl 10.201.218.182
|
| Dear Richard,
|
| Thank you for posting here.
|
| I understand that the process MsMpEng.exe and MOMHost.exe processes are
| creating a significant number of page faults on several servers.
|
| According to your description, it appears that the issue should not on
the
| SQL Server side. Based on my experience, this behavior can occur due to a
| Memory Leak but sometimes it is normal for some processes. In order to
| ensure the current status, I would like to confirm the following
| information before going further:
|
| 1. Has the performance on these severs been affected due to this issue?
|
| 2. Please also use the Performance Monitor utility to monitor the
stability
| of memory pages used by these two processes.
|
| To do so, please refer to the following steps:
| --
| a. Enter the Control Panel -> Administrative Tools -> Performance.
| b. Select "Process" in the "Performance object" selection
| c. Add the following counter for the two processes (MsMpEng.exe and
| MOMHost.exe) in question:
|
| - Working Set (The Working Set is the set of memory pages touched
recently
| by the threads in the process)
| - Virtual Bytes (Virtual Bytes is the current size, in bytes, of the
| virtual address space the process is using)
|
| NOTE: You can also add some main process for this server. E.X:
sqlservr.exe
| process
|
| d. If the indication goes very smoothly, it indicates that the memory
usage
| of these processes is stable. In opposition, the memory leak issue may
| exist.
|
| At the same time, on the SQL Server side, we can attempt to adjust the
| memory to see if it helps. Below are the detail steps:
| --
| a. Open the SQL Server Management Studio
| b. Right click on the SQL Server instance->choose Properties.
| c. Click on the Memory tab on the left panel, adjust the memory for your
| SQL Server.
|
| Have a nice day!
|
| Best regards,
|
| Adams Qu
| MCSE, MCDBA, MCTS
| Microsoft Online Support
|
| Microsoft Global Technical Support Center
|
| Get Secure! - www.microsoft.com/security
| =====================================================| When responding to posts, please "Reply to Group" via your newsreader so
| that others may learn and benefit from your issue.
| =====================================================| This posting is provided "AS IS" with no warranties, and confers no
rights.
|
| --
| | From: "Richard Perry" <RichardPerry@.newsgroup.nospam>
| | References: <3BFD2358-2798-4A29-B54A-EA90AD883293@.microsoft.com>
| <OBAYHbCDIHA.3712@.TK2MSFTNGP02.phx.gbl>
| | Subject: Re: Excessive Page Faults?
| | Date: Thu, 11 Oct 2007 12:56:40 -0700
| | Lines: 1
| | Message-ID: <84D91F2A-E4A6-4933-B34B-72879DD28277@.microsoft.com>
| | MIME-Version: 1.0
| | Content-Type: text/plain;
| | format=flowed;
| | charset="iso-8859-1";
| | reply-type=response
| | Content-Transfer-Encoding: 7bit
| | X-Priority: 3
| | X-MSMail-Priority: Normal
| | Importance: Normal
| | X-Newsreader: Microsoft Windows Live Mail 12.0.1365
| | X-MimeOLE: Produced By Microsoft MimeOLE V12.0.1365
| | X-MS-CommunityGroup-PostID: {84D91F2A-E4A6-4933-B34B-72879DD28277}
| | X-MS-CommunityGroup-ThreadID: 3BFD2358-2798-4A29-B54A-EA90AD883293
| | X-MS-CommunityGroup-ParentID: 47993B93-4F51-47EE-BE41-7DBD1C4B8AF7
| | Newsgroups:
|
microsoft.public.exchange.admin,microsoft.public.security.forefront,microsof
| t.public.sqlserver.server
| | Path: TK2MSFTNGHUB02.phx.gbl
| | Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.security.forefront:71
| microsoft.public.sqlserver.server:27713
| microsoft.public.exchange.admin:47476
| | NNTP-Posting-Host: TK2MSFTNGHUB02.phx.gbl 127.0.0.1
| | X-Tomcat-NG: microsoft.public.sqlserver.server
| |
| | Thanks for the link to the article. This does give some additional
| | information, however the problem in the article points more to high CPU
| | utilization rather than high number of page faults. Perhaps since this
| also
| | includes the MOM components, I should try posting in that forum as the
| | Forefront group is fairly new?
| |
| | Richard
| |
| | "Betelgeuse" <betelgeuse@.news.postalias> wrote in message
| | news:OBAYHbCDIHA.3712@.TK2MSFTNGP02.phx.gbl...
| | > This is not an exchange issue...
| | >
| | > But take a look at
| | > http://geekswithblogs.net/Coleman/archive/2007/03/26/109906.aspx
| | >
| | >
| | > "Richard Perry" <RichardPerry@.newsgroup.nospam> wrote in message
| | > news:3BFD2358-2798-4A29-B54A-EA90AD883293@.microsoft.com...
| | >>I am noticing that an many of my servers (Server 2003 EE SP2 R2),
that
| the
| | >>MsMpEng.exe and MOMHost.exe processes are creating a significant
number
| of
| | >>page faults.
| | >>
| | >> For example, on my SQL 2000 SP4 server with 4GB RAM which has been
up
| for
| | >> 19 days has nearly 19M page faults on MsMpEng and over 16M faults on
| | >> MOMHost.
| | >>
| | >> Another example is my Exchange 2003 SP2 with 4GB RAM which has also
| been
| | >> up for 19 days has nearly 182M faults on MsMpEng and nearly 16M
faults
| on
| | >> MOMHost.
| | >>
| | >> Keep in mind that the "M" with the number is million.
| | >>
| | >> We only recently started using Forefront on our servers, and this
| appears
| | >> to be a relatively new issue, and I would like to know if others
have
| | >> been experiencing this as well.
| | >>
| | >> Richard
| | >
| | >
| |
|
||||Sorry for the long delay in replying to this post. With the fires here is
SoCal, things have been fairly hectic.
Following your suggestions, I am verified that there is not a memory leak
with regards to these processes. Therefore, I am left with the simple
concern of the performance of Forefront on the Server platform. I will raise
this issue in the Forefront forums.
I do have a recurring issue with timeouts to the database that I am
troubleshooting, and it was this issue that prompted my looking at the
paging performance. I have consistently believed that the cause if these
timeouts is due to our network configuration, but for the sake of
completeness, I have been verifying our SQL setup. I will post regarding
those timeouts in another thread.
Sophie Tan, if you see this, I wanted to thank you for your follow up post
as well. At this time, I would consider this thread closed.
Richard Perry
"Adams Qu [MSFT]" <v-adamqu@.online.microsoft.com> wrote in message
news:8LjAyJKDIHA.4664@.TK2MSFTNGHUB02.phx.gbl...
> Dear Richard,
> Thank you for posting here.
> I understand that the process MsMpEng.exe and MOMHost.exe processes are
> creating a significant number of page faults on several servers.
> According to your description, it appears that the issue should not on the
> SQL Server side. Based on my experience, this behavior can occur due to a
> Memory Leak but sometimes it is normal for some processes. In order to
> ensure the current status, I would like to confirm the following
> information before going further:
> 1. Has the performance on these severs been affected due to this issue?
> 2. Please also use the Performance Monitor utility to monitor the
> stability
> of memory pages used by these two processes.
> To do so, please refer to the following steps:
> --
> a. Enter the Control Panel -> Administrative Tools -> Performance.
> b. Select "Process" in the "Performance object" selection
> c. Add the following counter for the two processes (MsMpEng.exe and
> MOMHost.exe) in question:
> - Working Set (The Working Set is the set of memory pages touched recently
> by the threads in the process)
> - Virtual Bytes (Virtual Bytes is the current size, in bytes, of the
> virtual address space the process is using)
> NOTE: You can also add some main process for this server. E.X:
> sqlservr.exe
> process
> d. If the indication goes very smoothly, it indicates that the memory
> usage
> of these processes is stable. In opposition, the memory leak issue may
> exist.
> At the same time, on the SQL Server side, we can attempt to adjust the
> memory to see if it helps. Below are the detail steps:
> --
> a. Open the SQL Server Management Studio
> b. Right click on the SQL Server instance->choose Properties.
> c. Click on the Memory tab on the left panel, adjust the memory for your
> SQL Server.
> Have a nice day!
> Best regards,
> Adams Qu
> MCSE, MCDBA, MCTS
> Microsoft Online Support
> Microsoft Global Technical Support Center
> Get Secure! - www.microsoft.com/security
> =====================================================> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> =====================================================> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> --
> | From: "Richard Perry" <RichardPerry@.newsgroup.nospam>
> | References: <3BFD2358-2798-4A29-B54A-EA90AD883293@.microsoft.com>
> <OBAYHbCDIHA.3712@.TK2MSFTNGP02.phx.gbl>
> | Subject: Re: Excessive Page Faults?
> | Date: Thu, 11 Oct 2007 12:56:40 -0700
> | Lines: 1
> | Message-ID: <84D91F2A-E4A6-4933-B34B-72879DD28277@.microsoft.com>
> | MIME-Version: 1.0
> | Content-Type: text/plain;
> | format=flowed;
> | charset="iso-8859-1";
> | reply-type=response
> | Content-Transfer-Encoding: 7bit
> | X-Priority: 3
> | X-MSMail-Priority: Normal
> | Importance: Normal
> | X-Newsreader: Microsoft Windows Live Mail 12.0.1365
> | X-MimeOLE: Produced By Microsoft MimeOLE V12.0.1365
> | X-MS-CommunityGroup-PostID: {84D91F2A-E4A6-4933-B34B-72879DD28277}
> | X-MS-CommunityGroup-ThreadID: 3BFD2358-2798-4A29-B54A-EA90AD883293
> | X-MS-CommunityGroup-ParentID: 47993B93-4F51-47EE-BE41-7DBD1C4B8AF7
> | Newsgroups:
> microsoft.public.exchange.admin,microsoft.public.security.forefront,microsof
> t.public.sqlserver.server
> | Path: TK2MSFTNGHUB02.phx.gbl
> | Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.security.forefront:71
> microsoft.public.sqlserver.server:27713
> microsoft.public.exchange.admin:47476
> | NNTP-Posting-Host: TK2MSFTNGHUB02.phx.gbl 127.0.0.1
> | X-Tomcat-NG: microsoft.public.sqlserver.server
> |
> | Thanks for the link to the article. This does give some additional
> | information, however the problem in the article points more to high CPU
> | utilization rather than high number of page faults. Perhaps since this
> also
> | includes the MOM components, I should try posting in that forum as the
> | Forefront group is fairly new?
> |
> | Richard
> |
> | "Betelgeuse" <betelgeuse@.news.postalias> wrote in message
> | news:OBAYHbCDIHA.3712@.TK2MSFTNGP02.phx.gbl...
> | > This is not an exchange issue...
> | >
> | > But take a look at
> | > http://geekswithblogs.net/Coleman/archive/2007/03/26/109906.aspx
> | >
> | >
> | > "Richard Perry" <RichardPerry@.newsgroup.nospam> wrote in message
> | > news:3BFD2358-2798-4A29-B54A-EA90AD883293@.microsoft.com...
> | >>I am noticing that an many of my servers (Server 2003 EE SP2 R2), that
> the
> | >>MsMpEng.exe and MOMHost.exe processes are creating a significant
> number
> of
> | >>page faults.
> | >>
> | >> For example, on my SQL 2000 SP4 server with 4GB RAM which has been up
> for
> | >> 19 days has nearly 19M page faults on MsMpEng and over 16M faults on
> | >> MOMHost.
> | >>
> | >> Another example is my Exchange 2003 SP2 with 4GB RAM which has also
> been
> | >> up for 19 days has nearly 182M faults on MsMpEng and nearly 16M
> faults
> on
> | >> MOMHost.
> | >>
> | >> Keep in mind that the "M" with the number is million.
> | >>
> | >> We only recently started using Forefront on our servers, and this
> appears
> | >> to be a relatively new issue, and I would like to know if others have
> | >> been experiencing this as well.
> | >>
> | >> Richard
> | >
> | >
> |
>|||Dear Richard,
Thank you for posting back.
From your last post, we are glad to hear that the memory leak issue does
not exist after we verified manually on the server.
I also understand that another issue with timeouts to the database is
experienced. To help you resolve the issue more efficiently, I also would
like to share with you the following troubleshooting information. You can
try the following points before submitting the new thread.
Reference Information on the second issue
--
Based on my experience, the time-out connection issue can be concluded to
be caused by one of the following two factors commonly:
a. Caused by the network configuration (as you mentioned)
b. The second cause is that the SQL Server is running on a heavy load at
that time.
c. Application or hard driver factors.
Please use SQL Profiler and Perfmon to monitor your SQL Server to see what
happens if the connection timeout occurs.
I also would like to provide the following links for your reference:
HOW TO: Troubleshoot Application Performance with SQL Server
http://support.microsoft.com/kb/224587/en-us
Troubleshooting Performance Problems in SQL Server 2005
http://www.microsoft.com/technet/prodtechnol/sql/2005/tsprfprb.mspx
INF: Understanding and Resolving SQL Server 7.0 or 2000 Blocking Problems
http://support.microsoft.com/kb/224453/en-us
Hope above information is helpful. Once we see your new thread, we will be
glad to follow up and help you. If you have any other questions or
concerns, please do not hesitate to contact us. It is always my pleasure to
be of assistance.
Have a nice day!
Best regards,
Adams Qu
MCSE, MCDBA, MCTS
Microsoft Online Support
Microsoft Global Technical Support Center
Get Secure! - www.microsoft.com/security
=====================================================When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.
--
| From: "Richard Perry" <RichardPerry@.newsgroup.nospam>
| References: <3BFD2358-2798-4A29-B54A-EA90AD883293@.microsoft.com>
<OBAYHbCDIHA.3712@.TK2MSFTNGP02.phx.gbl>
<84D91F2A-E4A6-4933-B34B-72879DD28277@.microsoft.com>
<8LjAyJKDIHA.4664@.TK2MSFTNGHUB02.phx.gbl>
| Subject: Re: Excessive Page Faults?
| Date: Wed, 31 Oct 2007 16:54:13 -0700
| Lines: 2
| MIME-Version: 1.0
| Content-Type: text/plain;
| format=flowed;
| charset="iso-8859-1";
| reply-type=original
| Content-Transfer-Encoding: 7bit
| X-Priority: 3
| X-MSMail-Priority: Normal
| Importance: Normal
| X-Newsreader: Microsoft Windows Live Mail 12.0.1365
| X-MimeOLE: Produced By Microsoft MimeOLE V12.0.1365
| Message-ID: <#82$XlBHIHA.4768@.TK2MSFTNGP03.phx.gbl>
| Newsgroups: microsoft.public.sqlserver.server
| NNTP-Posting-Host: 209.242.152.130
| Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP03.phx.gbl
| Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.sqlserver.server:29221
| X-Tomcat-NG: microsoft.public.sqlserver.server
|
| Sorry for the long delay in replying to this post. With the fires here is
| SoCal, things have been fairly hectic.
|
| Following your suggestions, I am verified that there is not a memory leak
| with regards to these processes. Therefore, I am left with the simple
| concern of the performance of Forefront on the Server platform. I will
raise
| this issue in the Forefront forums.
|
| I do have a recurring issue with timeouts to the database that I am
| troubleshooting, and it was this issue that prompted my looking at the
| paging performance. I have consistently believed that the cause if these
| timeouts is due to our network configuration, but for the sake of
| completeness, I have been verifying our SQL setup. I will post regarding
| those timeouts in another thread.
|
| Sophie Tan, if you see this, I wanted to thank you for your follow up
post
| as well. At this time, I would consider this thread closed.
|
| Richard Perry
|
|
| "Adams Qu [MSFT]" <v-adamqu@.online.microsoft.com> wrote in message
| news:8LjAyJKDIHA.4664@.TK2MSFTNGHUB02.phx.gbl...
| > Dear Richard,
| >
| > Thank you for posting here.
| >
| > I understand that the process MsMpEng.exe and MOMHost.exe processes are
| > creating a significant number of page faults on several servers.
| >
| > According to your description, it appears that the issue should not on
the
| > SQL Server side. Based on my experience, this behavior can occur due to
a
| > Memory Leak but sometimes it is normal for some processes. In order to
| > ensure the current status, I would like to confirm the following
| > information before going further:
| >
| > 1. Has the performance on these severs been affected due to this issue?
| >
| > 2. Please also use the Performance Monitor utility to monitor the
| > stability
| > of memory pages used by these two processes.
| >
| > To do so, please refer to the following steps:
| > --
| > a. Enter the Control Panel -> Administrative Tools -> Performance.
| > b. Select "Process" in the "Performance object" selection
| > c. Add the following counter for the two processes (MsMpEng.exe and
| > MOMHost.exe) in question:
| >
| > - Working Set (The Working Set is the set of memory pages touched
recently
| > by the threads in the process)
| > - Virtual Bytes (Virtual Bytes is the current size, in bytes, of the
| > virtual address space the process is using)
| >
| > NOTE: You can also add some main process for this server. E.X:
| > sqlservr.exe
| > process
| >
| > d. If the indication goes very smoothly, it indicates that the memory
| > usage
| > of these processes is stable. In opposition, the memory leak issue may
| > exist.
| >
| > At the same time, on the SQL Server side, we can attempt to adjust the
| > memory to see if it helps. Below are the detail steps:
| > --
| > a. Open the SQL Server Management Studio
| > b. Right click on the SQL Server instance->choose Properties.
| > c. Click on the Memory tab on the left panel, adjust the memory for your
| > SQL Server.
| >
| > Have a nice day!
| >
| > Best regards,
| >
| > Adams Qu
| > MCSE, MCDBA, MCTS
| > Microsoft Online Support
| >
| > Microsoft Global Technical Support Center
| >
| > Get Secure! - www.microsoft.com/security
| > =====================================================| > When responding to posts, please "Reply to Group" via your newsreader so
| > that others may learn and benefit from your issue.
| > =====================================================| > This posting is provided "AS IS" with no warranties, and confers no
| > rights.
| >
| > --
| > | From: "Richard Perry" <RichardPerry@.newsgroup.nospam>
| > | References: <3BFD2358-2798-4A29-B54A-EA90AD883293@.microsoft.com>
| > <OBAYHbCDIHA.3712@.TK2MSFTNGP02.phx.gbl>
| > | Subject: Re: Excessive Page Faults?
| > | Date: Thu, 11 Oct 2007 12:56:40 -0700
| > | Lines: 1
| > | Message-ID: <84D91F2A-E4A6-4933-B34B-72879DD28277@.microsoft.com>
| > | MIME-Version: 1.0
| > | Content-Type: text/plain;
| > | format=flowed;
| > | charset="iso-8859-1";
| > | reply-type=response
| > | Content-Transfer-Encoding: 7bit
| > | X-Priority: 3
| > | X-MSMail-Priority: Normal
| > | Importance: Normal
| > | X-Newsreader: Microsoft Windows Live Mail 12.0.1365
| > | X-MimeOLE: Produced By Microsoft MimeOLE V12.0.1365
| > | X-MS-CommunityGroup-PostID: {84D91F2A-E4A6-4933-B34B-72879DD28277}
| > | X-MS-CommunityGroup-ThreadID: 3BFD2358-2798-4A29-B54A-EA90AD883293
| > | X-MS-CommunityGroup-ParentID: 47993B93-4F51-47EE-BE41-7DBD1C4B8AF7
| > | Newsgroups:
| >
microsoft.public.exchange.admin,microsoft.public.security.forefront,microsof
| > t.public.sqlserver.server
| > | Path: TK2MSFTNGHUB02.phx.gbl
| > | Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.security.forefront:71
| > microsoft.public.sqlserver.server:27713
| > microsoft.public.exchange.admin:47476
| > | NNTP-Posting-Host: TK2MSFTNGHUB02.phx.gbl 127.0.0.1
| > | X-Tomcat-NG: microsoft.public.sqlserver.server
| > |
| > | Thanks for the link to the article. This does give some additional
| > | information, however the problem in the article points more to high
CPU
| > | utilization rather than high number of page faults. Perhaps since this
| > also
| > | includes the MOM components, I should try posting in that forum as the
| > | Forefront group is fairly new?
| > |
| > | Richard
| > |
| > | "Betelgeuse" <betelgeuse@.news.postalias> wrote in message
| > | news:OBAYHbCDIHA.3712@.TK2MSFTNGP02.phx.gbl...
| > | > This is not an exchange issue...
| > | >
| > | > But take a look at
| > | > http://geekswithblogs.net/Coleman/archive/2007/03/26/109906.aspx
| > | >
| > | >
| > | > "Richard Perry" <RichardPerry@.newsgroup.nospam> wrote in message
| > | > news:3BFD2358-2798-4A29-B54A-EA90AD883293@.microsoft.com...
| > | >>I am noticing that an many of my servers (Server 2003 EE SP2 R2),
that
| > the
| > | >>MsMpEng.exe and MOMHost.exe processes are creating a significant
| > number
| > of
| > | >>page faults.
| > | >>
| > | >> For example, on my SQL 2000 SP4 server with 4GB RAM which has been
up
| > for
| > | >> 19 days has nearly 19M page faults on MsMpEng and over 16M faults
on
| > | >> MOMHost.
| > | >>
| > | >> Another example is my Exchange 2003 SP2 with 4GB RAM which has also
| > been
| > | >> up for 19 days has nearly 182M faults on MsMpEng and nearly 16M
| > faults
| > on
| > | >> MOMHost.
| > | >>
| > | >> Keep in mind that the "M" with the number is million.
| > | >>
| > | >> We only recently started using Forefront on our servers, and this
| > appears
| > | >> to be a relatively new issue, and I would like to know if others
have
| > | >> been experiencing this as well.
| > | >>
| > | >> Richard
| > | >
| > | >
| > |
| >
|