kevindockerty
asked on
Page file size ?
I have a server ( Windows 2003 ) running SQL Server DB and SSAS
We have 32GB of physical memory available
The DB and cubes are farly large 200GB DB's - 100GB cubes
What is the optimum size of the page file I should be using
I am aware that Microsoft recommend 1.5 * Phys RAM GB
( ie in my scemario 48GB page file would be recommended )
I am also aware that this recommendation relates to home PC's and not production servers running large SQL DB's
In practice this is too large as I am limited by local disk space - the alternative being to use a SAN drive which I dont want to do because of poor performance.
Is the 48GB really necessary ?
What would be the impact of reducing this and letting the physical RAM do the work ?
It has been suggested we reduce this page file to a very minimal size ie 1GB - what problems if any would this cause ?
We are trying to balance the slow read time of reading the disk for page file use whilst optimizing memory available for SQL services.
any thoughts?
Kev
We have 32GB of physical memory available
The DB and cubes are farly large 200GB DB's - 100GB cubes
What is the optimum size of the page file I should be using
I am aware that Microsoft recommend 1.5 * Phys RAM GB
( ie in my scemario 48GB page file would be recommended )
I am also aware that this recommendation relates to home PC's and not production servers running large SQL DB's
In practice this is too large as I am limited by local disk space - the alternative being to use a SAN drive which I dont want to do because of poor performance.
Is the 48GB really necessary ?
What would be the impact of reducing this and letting the physical RAM do the work ?
It has been suggested we reduce this page file to a very minimal size ie 1GB - what problems if any would this cause ?
We are trying to balance the slow read time of reading the disk for page file use whilst optimizing memory available for SQL services.
any thoughts?
Kev
On servers with adequate disk space, the pagefile on all disks combined should be configured up to twice the physical memory for optimal performance. Servers of lesser workloads or those tight on disk space should still try to use a pagefile total of at least equal to the amount of physical memory (+1 MB). This is the minimum amount of space required to create a memory dump in the event the server encounters a STOP event (blue screen).
Also, my advice is to set equal amount of paging space in "initial" (minimum) and "maximum".
hope this helps
max
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
thanks - useful link
An interesting point of view(in which i generally follow) can be found here http://www.petri.co.il/pagefile_optimization.htm.
bottom line. if there is another disk attached set the page file there (48gb)
hope that helps