High pages/sec.. memory pressure ?

When I see high pages/sec, does SQL go to the pagefile to read or write
pages that need to be flushed out of physical memory or to be retrieved into
physical memory?Yes, that is what the pages/sec counter is measuring.
What numbers are you seeing? If you average 20 pages/sec or less you
are within the design of a standard installation of sql server. If I
was seeing more than 20, I would be adding more memory after some
obvious checking (size of pagefile and its utilization: page file: %
usage) That will give you a good idea of how much benefit extra
memory will give you too
On Jan 1, 9:41=A0pm, "Hassan" <has...@.test.com> wrote:
> When I see high pages/sec, does SQL go to the pagefile to read or write
> pages that need to be flushed out of physical memory or to be retrieved in=to
> physical memory?|||It depends on how you have your memory configured. A better counter to
monitor for memory pressure is page life expectancy.
--
Jason Massie
Web: http://statisticsio.com
RSS: http://feeds.feedburner.com/statisticsio
"Hassan" <hassan@.test.com> wrote in message
news:%23NNZlIQTIHA.280@.TK2MSFTNGP03.phx.gbl...
> When I see high pages/sec, does SQL go to the pagefile to read or write
> pages that need to be flushed out of physical memory or to be retrieved
> into physical memory?|||I'd also veryfy whether pages/sec was caused by the SQL Server process or by
some other apps.
Linchi
"Hassan" wrote:
> When I see high pages/sec, does SQL go to the pagefile to read or write
> pages that need to be flushed out of physical memory or to be retrieved into
> physical memory?
>|||How do you verify that Linchi ?
"Linchi Shea" <LinchiShea@.discussions.microsoft.com> wrote in message
news:5C03FF55-90CE-4B88-9D9E-6AC3B562EB34@.microsoft.com...
> I'd also veryfy whether pages/sec was caused by the SQL Server process or
> by
> some other apps.
> Linchi
> "Hassan" wrote:
>> When I see high pages/sec, does SQL go to the pagefile to read or write
>> pages that need to be flushed out of physical memory or to be retrieved
>> into
>> physical memory?
>>|||You can check page faults/sec for the SQL Server process either under the
perfmon instance Process\<sql process> or using Task Manager by adding the
page faults column on the Processes tab. Now, page faults are not a hard
paging indicator for the process as Pages/sec is for the OS. That is, you
can't necessarily say that a process is causing hard paging if it has high
page faults. But page faults may give you an indication. So if you see no
other process but the SQL process incurring page faults that nicely correlate
with the occurence of hard paging, you have reason to suspect the hard paging
si caused by the SQL process.
Linchi
"Hassan" wrote:
> How do you verify that Linchi ?
> "Linchi Shea" <LinchiShea@.discussions.microsoft.com> wrote in message
> news:5C03FF55-90CE-4B88-9D9E-6AC3B562EB34@.microsoft.com...
> > I'd also veryfy whether pages/sec was caused by the SQL Server process or
> > by
> > some other apps.
> >
> > Linchi
> >
> > "Hassan" wrote:
> >
> >> When I see high pages/sec, does SQL go to the pagefile to read or write
> >> pages that need to be flushed out of physical memory or to be retrieved
> >> into
> >> physical memory?
> >>
> >>
>