SQL Server Performance Forum – Threads Archive
Paging files
On one of my servers I have 2 paging files on the same physical disk (Disk #0 C:, E<img src=’/community/emoticons/emotion-1.gif’ alt=’
‘ />.<br /><br />Can this degrade server’s performance?<br /><br />CanadaDBA
quote:When you set the paging file size in Windows, the documentation states that the largest paging file that you can select is 4,095 megabytes (MB). This limit is imposed by the page mapping that we use on x86 processors. These processors cannot handle more pages per page file. This is the limit set per volume; you can actually create paging files this large on one or more drives if you need a larger paging file. If extra drives or volumes are not available, you can create multiple paging files on a single drive by placing them in separate folders.
Satya SKJ
Microsoft SQL Server MVP
Writer, Contributing Editor & Moderator
http://www.SQL-Server-Performance.Com
This posting is provided AS IS with no rights for the sake of knowledge sharing. The greatest discovery of my generation is that a human being can alter his life by altering his attitudes of mind.
on a properly configured dedicated SQL Server system
there should be almost no paging activity,
if there is, find out why and fix it
after that, you really shouldn’t need more than 1 2-3GB page file
realistically, you are not going to wait for a full dump of memory to the pagefile
i think the default is to do a small dump
I have 16GB RAM and in another post I am trying to force my server to use it. The server is using about 3GB RAM and 3GB of paging files. The paging files are located on C: and E: which are located on one physical disk. I am suspect that the server is not configured properly. I want to know if having two paging files on same disk hurts my server. And how can I resolve it? I want to minimize paging to harddisk.
quote:Originally posted by joechang
on a properly configured dedicated SQL Server system
there should be almost no paging activity,
if there is, find out why and fix it
after that, you really shouldn’t need more than 1 2-3GB page file
realistically, you are not going to wait for a full dump of memory to the pagefile
i think the default is to do a small dump
there should be almost no paging activity,
if there is, find out why and fix it
after that, you really shouldn’t need more than 1 2-3GB page file
realistically, you are not going to wait for a full dump of memory to the pagefile
i think the default is to do a small dump
CanadaDBA
Yes it hurts having 2 on the same disk, its better to manage the pagefile on a larger volume and avoid keeping data/log files of SQL Server there. Satya SKJ
Microsoft SQL Server MVP
Writer, Contributing Editor & Moderator
http://www.SQL-Server-Performance.Com
This posting is provided AS IS with no rights for the sake of knowledge sharing. The greatest discovery of my generation is that a human being can alter his life by altering his attitudes of mind.
If you’re talking about sql server, the only way i know to address more than 2,5-3 gb of ram is using AWE as memory model.
The memory problem is solved and my server is utilizing close to 16GB RAM. I like Joe’s comment and hilighted it in red. How can I minimize the paging activity?
quote:Originally posted by joechang
on a properly configured dedicated SQL Server system
there should be almost no paging activity,
if there is, find out why and fix it
after that, you really shouldn’t need more than 1 2-3GB page file
realistically, you are not going to wait for a full dump of memory to the pagefile
i think the default is to do a small dump
there should be almost no paging activity,
if there is, find out why and fix it
after that, you really shouldn’t need more than 1 2-3GB page file
realistically, you are not going to wait for a full dump of memory to the pagefile
i think the default is to do a small dump
CanadaDBA
]]>