Page Life Expectancy average 1

Last Post 10 Mar 2008 10:27 AM by jkeyzer. 13 Replies.
AddThis - Bookmarking and Sharing Button Printer Friendly
  •  
  •  
  •  
  •  
  •  
Sort:
PrevPrev NextNext
You are not authorized to post a reply.
Author Messages
jkeyzer
New Member
New Member

--
06 Mar 2008 01:40 PM
I just viewed Kevin Kline's screencast titled "SQL Server Performance Counters for tracking Windows Memory" and have a question.
Page Life Expectancy shows average of 1, but the other counters look good I think
Available Mbytes shows average 1072,
Pages Input/Sec average 0,
Pages/Sec average 0,
Memory Grants Pending average 0.

What else should I check to identify why Page Life Expectancy is so low?
jkeyzer
New Member
New Member

--
07 Mar 2008 04:24 AM
Yes these are counteres from Perfmon. I watched the counters about 1/2 hour yesterday and about the same this morning. The counters are a little different this morning.
Page Life Expectancy shows average of 6,
Available Mbytes shows average 1190,
Pages Input/Sec average 492,
Pages/Sec average 492,
Memory Grants Pending average 0.
SQLUSA
New Member
New Member

--
07 Mar 2008 04:55 AM
Can you describe your platform?

You maybe low on memory?

Can you also give details of apps and batches running?

A batch job can force OLTP pages out of memory.

Kalman Toth - Database, Data Warehouse & Business Intelligence Architect
BI Workshop NYC SSRS, SSIS, SSAS - March 17-20: http://www.sqlusa.com/order2005bitr...008031720/


jkeyzer
New Member
New Member

--
07 Mar 2008 10:21 AM
Windows 2003 sp1 32 bit / SQL Server 2005 Enterprize edition SP2 (9.00.3042.00). The maghine has 4 Gig of memory. awe has not been enabled. tempdb is 5gig. There are about 40 databases on the server which occupy about 180 Gig. SQL Server and reporting services are all that is running on the machine.
jkeyzer
New Member
New Member

--
07 Mar 2008 11:39 AM
/3gb is in the boot.ini bu I am not sure that the server has been stopped after it was added. SQL Server memory is min 128 and max 2147483647. Task Manager show sqlserver.exe using 1,789,404KB.
jkeyzer
New Member
New Member

--
07 Mar 2008 11:43 AM
The scale for PLE is set to 1.
jkeyzer
New Member
New Member

--
07 Mar 2008 01:00 PM
Would it help to use the /userva switch?
jkeyzer
New Member
New Member

--
10 Mar 2008 06:39 AM
Thanks. So how much memory should I add and how should Windows, SQL Server, Reporting Services, and possible analysis service be configured to utilize the memory?
jkeyzer
New Member
New Member

--
10 Mar 2008 10:27 AM
The install procedure doesn't give us the option to put the services on different servers.
jkeyzer
New Member
New Member

--
10 Mar 2008 12:32 PM
The install of the application doesn't give us the option to specify different servers when we are installing it. The app assumes that sql server and reporting services are on the same server.
jkeyzer
New Member
New Member

--
11 Mar 2008 05:14 AM
The app we are installing is for storing source code and requires both SQL Server and Reporting Services on the same server.
SQLUSA
New Member
New Member

--
12 Mar 2008 11:05 PM
That is true. RS is usually married to SQL Server.

However, you can choose not to install Reporting Services. Instead you can install it on a different server with SQL Server 2005(required).

Have you noticed though that Reporting Services is the real issue? You see lots of memory usage by RS?

Why don't you buy more memory? It is dirt cheap.

Kalman Toth - Database, Data Warehouse & Business Intelligence Architect
BI Workshop NYC - March 17-20: http://www.sqlusa.com/order2005bitr...008031720/
SQLUSA
New Member
New Member

--
13 Mar 2008 02:11 AM
Very interesting Russell.

Reporting Services requires though 2 databases. So putting it on a virgin web server does not fully locate it there.

Can you explain us the pros and cons of such a configuration?

Kalman Toth - Database, Data Warehouse & Business Intelligence Architect
BI Workshop NYC SSRS - March 17-20: http://www.sqlusa.com/
TRACEYSQL
New Member
New Member

--
15 Mar 2008 06:23 AM
Just curious why only 4 gig on SQL 2005 license only is 25k ...memory will only cost around few hundred, is the server capable of adding more memory.

180 GIG databases thats got to be hurting in performance.

There is a three page document on switches 32/64 bit memory in March 2008 issue very good read tells you when to do the switch etc.

You might want to shrink your tempdb if its large .
You are not authorized to post a reply.

Acceptable Use Policy