Hello ...
Let's say we're configuring our 2000 Advanced Server machines with 3 NTFS drives - one for the NOS, one for the Program Files and another for the Data.
How would you split the Paging File across these drives keeping in mind we would like to keep the memory dump file??
My thinking is to split it across the non-NOS drives - D: & E:, with the first allocated size (on D:) being the amount of RAM installed and the second (on E:) being 1/2 the total RAM. i.e. with 1GB of RAM, making D: a total of 1GB and E: a total of 512MB.
I read somewhere that you probably don't want to keep too large a paging file on your NOS partition. Am I correct? Any suggestions? Recommendations from experience with Windows 2000?
I'm not just looking for an answer, but also a 'why' ...
Thanks!
Chris.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Yep - the servers will have have RAID redundancy across 5 physical drives. They'll be large, but I'm not sure what size right now - space shouldn't be a problem.
If the system is RAID-5 and it's being striped across all drives, does it really matter if it's all sitting on one logical partition?
Chris.
Based on what MS suggested, it is better to allocate different page file onto different logical partition and different physical hard disks. Also, the way you mentioned about D: and E: page file size may not be right, because you certainly need a page file on NOS drive too (actually the system will not allow you to remove all page file from NOS drive, at least 2 MB I remember). Anyway, the link below will explain details about what is requierd and why
http://support.microsoft.c
Generally the performance option is place the pagefile on a seperate drive to the system.
But more realistically the page file should be placed on a drive doing the least amount of work instead.
Just review the performance of your system and adjust where the file goes.
I still use the of 2*ram for initial size but if your running applications like SQL server then i would suggest that more than 50% of ram size pagefile activity means install real Ram to maintain performance.
Business Accounts
Answer for Membership
by: bitmapPosted on 2000-08-14 at 07:09:52ID: 3918814
I assume that these are 3 physically different drives? If it is one drive split into 3 partitions, there is very little if any benefit to breaking the page file across drives. The reason you want to keep the page file off the NOS drive is because the NOS partition will be used a lot during normal operation. Since a drive can only do one thing at a time, if it is reading files for the OS it can't be writing data to a pagefile. If it is on a separate drive, this can happen simultaneously. Also, the pagefile can use up quite a bit of space, if it fills up and the OS uses up a lot of TEMP space, the NOS drive can run out of space and possibly crash.
Sorry, I don't have any 2000 specific info, I'm just getting started with it.