Memory tweaking is an important part of the System Administrator's responsibilities. Having too much memory won't hurt you, but this is something we cannot expect to have all the time. This page will give you some working tips on memory management for Windows 2000, Windows XP and Windows Server 2003.
A program instruction on an Intel 386 or later CPU can address up to 4GB of memory, using its full 32 bits. This is normally far more than the RAM of the machine, so the hardware provides for programs to operate in terms of as much as they wish of this full 4GB space as Virtual Memory, those parts of the program and data which are currently active being loaded into Physical Random Access Memory (RAM). The processor itself then translates (‘maps’) the virtual addresses from an instruction into the correct physical equivalents, doing this on the fly as the instruction is executed. The processor manages the mapping in terms of pages of 4 Kilobytes each - a size that has implications for managing virtual memory by the system.
Optimizing your page file when you're running low on RAM is always a good idea. How much swap space do you need? That depends the amount of RAM you have and the programs you use. The rule of the thumb is 1.5 times the amount of system memory, unless you have too much load on your system.
Strictly speaking Virtual Memory is always in operation and cannot be ‘turned off’. What is meant by such wording is ‘set the system to use no page file space at all’. This would waste a lot of the RAM. The reason is that when programs ask for an allocation of Virtual memory space, they may ask for a great deal more than they ever actually bring into use - the total may easily run to hundreds of megabytes..................
Get Professionally written Essays that are:
• Written According to your Exact Requirements
• 100% Original and Non-Plagiarized
• Written by Expert
UK Writers
• Delivered to you before your deadline
Amazingly Low Prices - £9.95/page
