Advertisement

04.05.2004 at 04:58AM PDT, ID: 20943708
[x]
Attachment Details
[x]
The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

  • The Grade of the Solution
  • The Zone Rank of the Expert Providing the Solution
  • The Number of Author and Expert Comments
  • The Number of Experts Contributing
  • The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!

page file size and location

Tags: page, file, size, location
I am running ntserver 4 with the following disk structure:
1st physical disk; 2 gig partition for O/S, extended partition on this disk is logical drive of 38 gig for apps and data.
2nd physical disk; logical drive of 80 gigs (nothing on here, just used for backups and storage)
I went from 512 Megs of RAM to 1000. My page file is now to small (512 to 562 max). Microsoft recommends putting your page file to a separate disk  (or at least a different partition than your system partition) and leaving the original on the system partition for memory dumps. As it stands now, I have a notification in event viewer that my crash dump is disabled due to memory size.
If I understand the recommendations, I should have a page file equal to one and a half times my physical memory. Obviously, I can’t do that on the system partition. So, I’m trying to determine the best way to create my page files; should I increase the one on my system partition? Put one the data partition? Put one on the second disk? How do I determine the initial size and the maximum size for each?
Thanks


Start your free trial to view this solution
Question Stats
Zone: OS
Question Asked By: capvac
Solution Provided By: sirbounty
Participating Experts: 1
Solution Grade: A
Views: 38
Translate:
Loading Advertisement...
04.05.2004 at 05:02AM PDT, ID: 10756553

All comments and solutions are available to Premium Service Members only.

Start your 7-day free trial and see for yourself why Experts Exchange is the easiest and most proven technology resource in the world. Get Started

Already a member? Login to view this solution.

 
04.05.2004 at 05:30AM PDT, ID: 10756739

All comments and solutions are available to Premium Service Members only.

Start your 7-day free trial and see for yourself why Experts Exchange is the easiest and most proven technology resource in the world. Get Started

Already a member? Login to view this solution.

 
04.05.2004 at 10:03AM PDT, ID: 10759024

All comments and solutions are available to Premium Service Members only.

Start your 7-day free trial and see for yourself why Experts Exchange is the easiest and most proven technology resource in the world. Get Started

Already a member? Login to view this solution.

 
04.05.2004 at 07:31PM PDT, ID: 10762646

All comments and solutions are available to Premium Service Members only.

Start your 7-day free trial and see for yourself why Experts Exchange is the easiest and most proven technology resource in the world. Get Started

Already a member? Login to view this solution.

 
 
Loading Advertisement...
Microsoft
  • Internet Protocols
  • Applications
  • Development
  • OS
  • Hardware
  • Windows Security
Apple
  • Operating Systems
  • Hardware
  • Programming
  • Networking
  • Software
Internet
  • Search Engines
  • File Sharing
  • WebTrends / Stats
  • Spy / Ad Blockers
  • Web Browsers
  • New Net Users
  • Web Development
  • Chat / IM
  • Anti Spam
  • Web Servers
  • Anti-Virus
  • Email Clients
Gamers
  • Tips
  • Online / MMORPG
  • Puzzle
  • Emulators
  • Action / Adventure
  • Role Playing
  • Consoles
  • Game Programming
  • Strategy
  • Sports
  • Misc
  • Computer Games
Digital Living
  • Hardware
  • Automotive
  • New Net Users
  • New Users
  • Software
  • Digital Music
  • Gaming World
  • Home Security
  • Apple
  • Networking Hardware
Virus & Spyware
  • Vulnerabilities
  • IDS
  • Encryption
  • Anti-Virus
  • Operating Systems Security
  • Software Firewalls
  • WebApplications
  • Cell Phones
  • Operating Systems
  • Internet
  • Hardware Firewalls
Hardware
  • Displays / Monitors
  • Handhelds / PDAs
  • Components
  • Peripherals
  • Laptops/Notebooks
  • Servers
  • Misc
  • Apple
  • Embedded Hardware
  • Networking Hardware
  • Storage
  • Desktops
  • New Users
Software
  • System Utilities
  • Industry Specific
  • Network Management
  • Photos / Graphics
  • Page Layout
  • VMware
  • Misc
  • Web Development
  • OS
  • CYGWIN
  • Voice Recognition
  • Virtualization
  • Message Queue
  • Quality Assurance
  • Security
  • Firewalls
  • MultiMedia Applications
  • Development
  • Database
  • Office / Productivity
  • Business Management
  • OS/2 Apps
  • Server Software
  • Internet / Email
ITPro
  • OS
  • Storage
  • Encryption
  • Operating Systems Security
  • Apple Hardware
  • Laptops & Notebooks
  • Servers
  • Networking Hardware
  • Peripherals
  • Devices
  • Displays / Monitors
  • WebTrends / Stats
  • Search Engines
  • Firewalls
  • Web Computing
  • WebApplications
  • IDS
  • Vulnerabilities
  • Email Clients
  • File Sharing
  • Spy / Ad Blockers
  • Web Browsers
  • Web Servers
  • Networking
  • Anti-Virus
  • Consulting
  • Chat / IM
  • Anti Spam
Developer
  • Web Servers
  • Web Browsers
  • Game Programming
  • Dev Tools
  • Industry Specific
  • Office / Productivity
  • Database
  • CYGWIN
  • Web Development
  • Search Engines
  • File Sharing
  • WebTrends / Stats
  • Programming
  • Content Management
  • Application Servers
  • Protocols
Storage
  • Removable Backup Media
  • Storage Technology
  • Servers
  • Grid
  • Remote Access
  • Backup / Restore
  • Misc
  • Hard Drives
OS
  • Miscellaneous
  • Security
  • Development
  • Linux
  • VMware
  • MainFrame OS
  • Unix
  • Apple
  • OS / 2
  • AS / 400
  • BeOS
  • Microsoft
  • VMS / OpenVMS
Database
  • Oracle
  • Miscellaneous
  • MySQL
  • Software
  • Sybase
  • Contact Management
  • PostgreSQL
  • Data Manipulation
  • Clarion
  • InterSystems Cache
  • Siebel
  • MUMPS
  • OLAP
  • SQLBase
  • SAS
  • GIS & GPS
  • 4GL
  • Berkeley DB
  • DB2
  • Informix
  • Interbase / Firebird
  • FoxPro
  • Reporting
  • LDAP
  • Filemaker Pro
  • MS SQL Server
  • dBase
  • MS Access
Security
  • Misc
  • Web Browsers
  • Software Firewalls
  • Operating Systems Security
  • File Sharing
  • Spy / Ad Blockers
  • Vulnerabilities
  • WebApplications
  • IDS
  • Anti-Virus
  • Encryption
  • Anti Spam
  • Email Clients
  • VPN
  • Chat / IM
Programming
  • Editors IDEs
  • Installation
  • Handhelds / PDAs
  • Multimedia Programming
  • System / Kernel
  • Automation
  • Algorithms
  • Game
  • Signal Processing
  • Project Management
  • Open Source
  • Database
  • Misc
  • Languages
  • Processor Platforms
  • Theory
Web Development
  • Scripting
  • Blogs
  • Web Servers
  • Software
  • Search Engines
  • Web Graphics
  • Web Services
  • Images
  • Internet Marketing
  • Images and Photos
  • Components
  • Document Imaging
  • Web Languages/Standards
  • Illustration
  • WebApplications
  • Fonts
  • WebTrends / Stats
  • Authoring
  • Digital Camera Software
  • Miscellaneous
Networking
  • Protocols
  • Apple Networking
  • Network Management
  • Message Queue
  • Application Servers
  • Content Management
  • File Servers
  • Email Servers
  • Misc
  • Java Editors & IDEs
  • Wireless
  • Networking Hardware
  • Backup / Restore
  • System Utilities
  • ISPs & Hosting
  • Web Servers
  • Storage Technology
  • Removable Backup Media
  • Servers
  • Web Computing
  • Broadband
  • Grid
  • OS / 2
  • Novell Netware
  • Unix Networking
  • Windows Networking
  • Security
  • Telecommunications
  • Operating Systems
  • Linux Networking
Other
  • Lounge
  • Business Travel
  • Community Support
  • New Net Users
  • Philosophy / Religion
  • Math / Science
  • Miscellaneous
  • URLs
  • Expert Lounge
  • Politics
  • Puzzles / Riddles
  • Automotive
Community Support
  • Suggestions
  • New to EE
  • New Topics
  • CleanUp
  • Announcements
  • General
  • Feedback
  • Input
  • EE Bugs
 
04.05.2004 at 05:02AM PDT, ID: 10756553
>>
By default, Windows places the pagefile on the boot partition where the operating system is installed. To determine the size of the pagefile multiply the amount of physical RAM by 1.5 to a maximum of 4095MB. However, placing the pagefile on the boot partition does not optimize performance because Windows has to perform disk I/O on both the system directory and the pagefile. Therefore, it is recommended that you place the pagefile on a different partition and different physical hard disk drive so that Windows can handle multiple I/O requests more quickly.

However, completely removing the pagefile from the boot partition does not allow Windows to create a crash dump file (Memory.dmp) should a kernel mode STOP error occur. Not having this crash dump file could lead to extended server downtime should the STOP require a debug to be performed.

The optimal solution is to create one pagefile on the boot partition using the default settings and create one pagefile on another less frequently used partition. The best option is to create the second pagefile so that it is on its own partition, with no data or operating system-specific files.

Windows will use the pagefile on the less frequently used partition over the pagefile on the heavily used boot partition. Windows uses an internal algorithm to determine which page file to use for virtual memory management. In the above scenario, the following goals of the page file would be served:


The system will be properly configured to capture a Memory.dmp file should the computer experience a kernel mode STOP error.
The page file on the less frequently used partition will be used the majority of the time because it is not on a busy partition.
<<ref:http://support.microsoft.com/?kbid=197379
 
04.05.2004 at 05:30AM PDT, ID: 10756739
>>The only downside to a too large page file size is that you are consuming some of your disk space unneccessarily. Given the size of modern disks, this seems to be a trivial issue. Under Windows NT, the page file occupies a contiguous block of space in the partition. If possible split the page file between hard disks. Don't split the page file across partitions created on the same hard drive since that will decrease performance.

The downsides of a too small pagesize are much more serious. At a minimum, your system will experience disk thrashing where your pagefile files to maximum and NT is constantly swapping out segments of RAM to disk virtual memory. This can really impact performance. It can also result in a corrupted pagefile. Additionally, the pagesize should be at least the size of RAM+1MB in order to support core dumps. In any case, you have swapped out the fasted component in your server for the slowest. <<
ref: http://is-it-true.org/nt/atips/atips178.shtml
Also: http://www.forensics-intl.com/def7.html
 
04.05.2004 at 10:03AM PDT, ID: 10759024
Ok, so set me straight here. I cant really put the proper size page file (for crash dumps) on the system partition because, the partition is only 2 gigs with 1.02 gigs free. I have 1 gig of physical memory on the board.
Should I leave that pagefile as is, or increase the size? If its not as big as the amount of RAM will it be effective in the event of a crashdump?
But, I can put a second page file on the second disk for virtual memory and I would configure it to be 1100 meg min? should I set the max to 1.5 times the ram? in this case 1.5 gigs?
thanks
 
04.05.2004 at 07:31PM PDT, ID: 10762646
>> If its not as big as the amount of RAM will it be effective in the event of a crashdump?<<
You may get a partial dump...but realistically, you may never have a system dump.
With windows 2000, you can specify the type of dump to use, but this option isn't available with NT Server...
When we were running NT servers, out of 90 - I think we may have had about 15% of those ever crash.
Odds are that you will be able to troubleshoot a problem even without a full dump (you've got experts-exchange ;)

I'd say, if you can boost it to a GB on the primary, and then set the second disk to 1536, you should run fine...
Accepted Solution
 
 
20080716-EE-VQP-33