August 18, 2014 at 4:03 am
1.Memory\Page Faults/sec
Min value = 1865.610193
Max value = 7440.700727
captured system perfmon tools for over 2 hour’s. What could be reason always more than 1500 values using memory page faults sec counter? Is it normal?
OS: win 2008 32 bit
DB: SQL 2008 32 bit
Physical memory = 16 GB (server is not dedicated SQL database also running other application services etc.)
Database AWE configured up 8GB and total 16 GB physical memory of server.
Lock page memory configured due to AWE enabled.
Max memory configured upto 8GB.
2.LogicalDisk(_Total)\Current Disk Queue Length
This counter values does not exceeding more than 1 during 2 hours intervals.
3.Memory Manager\Total Server Memory (KB), Memory Manager\Target Server Memory (KB) both are equal always = 8388608
Thanks
ananda
August 18, 2014 at 4:48 am
What's normal for this server for those counters?
Why are you looking at page faults specifically? Do you have a lot of non-SQL apps on the server which are getting paged out?
Why are you looking at disk queue length at all?
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
August 18, 2014 at 5:48 am
1. What's normal for this server for those counters?
I am not sure those counter normal values, It might be < 500 seconds for better (soft/hard page read seconds)
2. Why are you looking at page faults specifically?
How physical memory being used SQL as well as other application. I had checked private working set counter(Process(_Total)\Private Bytes), it is always more that 4720881664 ( 4.7 GB other application using currently)
3. Do you have a lot of non-SQL apps on the server which are getting paged out?
how did we check Non-SQL apps paged out or not? But DB & Apps should be same machine as per application architecture
August 18, 2014 at 6:19 am
SQL Galaxy (8/18/2014)
1. What's normal for this server for those counters?I am not sure those counter normal values, It might be < 500 seconds for better (soft/hard page read seconds)
Then you need to establish baselines. Without baselines for what is normal for the server you cannot make any sense of most perfmon counters.
3. Do you have a lot of non-SQL apps on the server which are getting paged out?
how did we check Non-SQL apps paged out or not? But DB & Apps should be same machine as per application architecture
Well, I assumed you'd know that, because having non-SQL apps with paging issues is one of the few reasons for looking at page faults/sec. SQL doesn't use the page file and, if it does get paged out there will be error messages. If you don't know, why are you looking at that counter? What do you expect to discover from it?
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
September 26, 2014 at 12:17 am
Hi Gail,
I am looking at the memory status in 3 of our production servers. This is to create a new database for a new application. I found the CPU usage is normal and under 10%. But regarding memory status I have the below values. Kindly suggest if the system memory is very less and due for an immediate upgrade and in worst case scenario which server should I choose to create the new database. The new database will have 25-30 users at a time with 20% growth per month.
Server1
Available Physical Memory281001984
Available Virtual Memory8771612917760
Available Paging File 20251398144
Working Set 15956381696
% of Committed Memory in WS100
Page Faults 606707900
Server2
Available Physical Memory1256210432
Available Virtual Memory8780392566784
Available Paging File 8549621760
Working Set 6213906432
% of Committed Memory in WS85
Page Faults 202220240
Server3
Available Physical Memory201707520
Available Virtual Memory8778526580736
Available Paging File 11492261888
Working Set 7418912768
% of Committed Memory in WS99
Page Faults 97029760
______________________________________________________________Every Problem has a Solution; Every Solution has a Problem: 🙂
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply