<! --INFOLINKS_ON-->
Virtual MemoryBack on the 'good old days' with command prompts and 1. 2MB floppy hard disk drives, programs needed very little RAM to move because the main (and almost universal) computer system was Microsoft DOS and your memory footprint was small. That was truly fortunate because RAM at the beginning was horrendously expensive. Although given that ludicrous, 4MB of RAM was considered then that should be an incredible amount from memory. However when Windows became a greater number of popular, 4MB was hardly enough. Due to the country's GUI (Graphical User Interface), it had an even better memory footprint than DOS. Subsequently, more RAM was wanted. Unfortunately, RAM prices will not decrease as fast seeing that RAM requirement had amplified. This meant that Windows users needed either fork out a lot for more RAM and run only simple programs. Neither were attractive solutions. An alternative method was wanted to alleviate this problem. The solution they located was to use some space to the hard disk as additional RAM. Although the harddrive is much slower rather than RAM, it is also a whole lot cheaper and users always have way more hard disk space than RAM. So, Windows was manufactured to create this pseudo-RAM or possibly in Microsoft's terms : Virtual Memory, to replace the shortfall in GOOD OLD RAM when running memory-intensive software. How Does It Succeed? Virtual memory is constructed with a special file generally known as a swapfile or paging report. Whenever the operating model has enough memory, aging usually use virtual mind. But if it runs out from memory, the operating system will page out a minimum recently used data while in the memory to the swapfile on the hard disk. This frees up some memory for use on your applications. The operating system will continuously do this as a greater number of data is loaded on the RAM. However, when any data stored on the swapfile is needed, it's always swapped with the least recently used data while in the memory. This allows a swapfile to behave including RAM although programs is unable to run directly off the application. You will also remember that because the operating process cannot directly run programs journey swapfile, some programs may not run besides a large swapfile if you suffer from too little RAM. Swapfile Against. Paging FileWe have all been aided by the terms swapfile and paging data file interchangeably. Even Microsoft invariably is the paging file being the swapfile and vice versa. Still, the swapfile and paging data are two different organisations. Although both are would always create virtual memory, there is subtle differences between the 2 main. The main difference is based on their names. Swapfiles operate by replacing entire processes from system memory throughout the swapfile. This immediately frees " up " memory for other applications to try. In contrast, paging files function by moving "pages" from the program from system memory towards the paging file. These pages are 4KB proportions. The entire program will never get swapped wholesale on the paging file. While swapping occurs any sort of accident heavy demand on the machine memory, paging can appear preemptively. This means that the main system can page out parts of a program within the next minimized or left idle for a long time. The memory used by your paged-out portions are not even immediately released for employ by other applications. In lieu, they are kept relating to standby. If the paged-out use is reactivated, it can instantly discover the paged-out parts (which continues to stored in system memory). But if another application requests for those memory space, then the device memory held by that paged-out data is released due to its use. As you are able to access, this is really quite totally different from the way a swapfile works out. Swapfiles were used around old iterations of Ms Windows, prior to Windows 7 95. From Windows 89 onwards, all Windows versions don't use anything except paging files. Therefore, an accurate term for the file familiar with create virtual memory in current os's is paging file, not likely swapfile. Because both swapfiles plus paging files do the same principal - create virtual mind, people will always relate to swapfiles and paging recordsdata interchangeably. Let's just try to remember their innate differences. Do We Still Apparent Paging File? Even now, when the average home user's computer contains at least 256MB involving RAM, the paging file 's still very important. While the number of RAM in the general user's computer makes also of memory shortage less of a worry by using single applications now than it was back then; the paging file is obviously important when multi-tasking. Note that after a period, the emphasis has evolved to multi-tasking. No longer will most people be solely stuck to make sure you using one application during the time. In fact, it is common to acquire 10 or more job applications running simultaneously! For model, I normally have the examples below applications running also: - + Microsoft Probability + Internet browsers like Maxthon and Firefox + Some sort of FTP client + Fast messengers like Trillian and MSN Messenger + Some download manager like FlashGet + Macromedia Dreamweaver + P2P individuals like ShareAza + A great antivirus software + Adobe Acrobat Reader by having a few PDF documents openedThat's earnings of 10-12 applications operating simultaneously! Even with 256MB with RAM, it would come to be impossible to load the whole thing into memory. A paging file will be store the least used data while in the memory so that I often open up all those applications You want. And let's not your investment disk cache. Operating systems like Windows 98 and Or windows 7 allocate a sizeable area of the RAM to the disk cache. This speeds up accesses to harddisk data by caching some of the most frequently used combined with data that are most likely to end up accessed next by a computer. This cuts down on the length of available RAM. So, with out paging file, you won't be prepared to open many applications although your computer has 256MB involving RAM. Finally, some programs require the installation of a paging file to operate properly. It may be that will store sensitive data at something less volatile compared to a RAM or to guarantee the computer will have sufficient memory running it. But whatever the grounds, a paging file is needed to help these programs to go. Why Optimize The Paging Data? Unless your computer is actually loaded with RAM, ?t's going to almost always use this paging file. As these, its performance affects the performance for the whole computer. Now, which has a paging file may be understood as a really cheap technique to run memory intensive programs without the presense of expense of buying more RAM. However, even the fastest harddisk is more than any order of magnitude slower versus the slowest RAM. Even the fastest harddisk is currently over 70X slower versus the dual-channel PC2700 DDR memory common in a great many computers. Let's not even start comparing the harddrive with faster RAM products like PC3200 DDR ram or PC2-4200 DDR2 memory. So, paging file is a stopgap solution for the void of sufficient RAM. As long just like you use the paging computer file, there will always come to be performance degradation. The ideal solution for insufficient RAM can be more RAM, not extra Virtual Memory. But since we can't afford lots of the RAM we want, a paging file is for us to operated today's memory guzzling systems. As you can say to, more isn't better for ones paging file because further paging file space will only offer ability to run a lot more memory intensive programs instantly. It will not hasten your system. But what we is capable of doing is to optimize the paging file in order that the performance degradation when utilizing it is minimized. So How should We Optimize The Paging Data file? There have been many theories on what to optimize the paging register. The most important ones are down the page: - + Making a paging file contiguous. + Moving the paging file to outer tracks of the drive. + Creating a great paging file. + Moving the paging file to an alternative partition in the same drive. + Moving the paging file to an alternative hard disk. + Creating multiple paging files + Moving the paging file towards RAID array + Transferring the paging file for a RAM drive + Limiting reliance on virtual memoryWe might examine those methods and then determine what will work plus what won't. Virtual Storage area Then And NowWindows 3. 1Back on the good old days connected with DOS 6. 22 not to mention Windows 3. 1, everyone knew that working with a permanent swapfile was the main factor to optimal swapfile general performance. This was because Home's windows 3. 1 only creates permanent swapfiles who are contiguous. A contiguous swapfile is mostly a swapfile that consists connected with an uninterrupted block of drive space. When a swapfile is definitely contiguous, the read-write heads for the hard disk can look over and write data to the swapfile in a constant fashion. In Windows 3. 1, if for example the swapfile was set up for a temporary swapfile which manufactured every time Windows 3. 1 hunter wellies up, it will end up in the final analysis of the hard hard disk drive and fragmented too. For that reason, every time the swapfile is normally read from or drafted to, the hard disk heads have to seek in platters to conduct these operations. Needless to tell you, this greatly erodes the performance for the swapfile. That's why it's important to make all the swapfile permanent in Glass windows 3. 1 - in order that the swapfile will become contiguous. Home's windows 95 And AboveFrom Windows 7 95 onwards, Microsoft encouraged the installation of its new dynamic exclusive memory system. Of lessons, there is nothing new for the virtual memory part although the keyword in this new technique is dynamic. The new dynamic virtual memory system no longer uses fixed-size swapfile but some sort of paging file that dynamically resizes itself reported by need. When the computer runs because of memory, more memory is created by increasing how large is the paging file. The moment the virtual memory is separated up, theoretically the paging file diminishes proportions. Microsoft claims that at the same time its dynamic virtual memory system will come up with a fragmented paging file, it's always still faster than Home's windows 3. 1's static internet memory system. As a definite plus, no hard disk space could be tied up in some permanent paging file. Still, this dynamic virtual memory system gives you a big disadvantage - it are not to be moved to the outer tracks for the hard disk platters. Dynamic Paging Files And additionally Data LocalityThere are men and women that assert that when placed alone, Windows XP will basically create virtual memory pages right next to frequently-used data in the drive, like documents. In alternative words, they claim that Or windows 7 monitors disk usage, maintains a database of frequently-used files on the hard disk and uses that information to set-up the paging file based upon spatial locality. With virtual memory pages created nearly frequently-used data, this apparently allows diminished seeks between frequently-used data and therefore the paging file. That is a premise behind their theory of letting Or windows 7 handle the paging data file dynamically. However, I don't even think this is true in the least. First of all, while Or windows 7 does monitor disk usage and a database of frequently-used computer files, only disk defragmenting functions use that database. All the built-in Disk Defragmenter, combined with third-party disk defragmenting functions, use this database to rearrange the harddrive so that frequently-used data files. But as far while I'm aware, the paging file doesn't arrange the location in the pages according to this database. From my observations, Windows XP simply employs the nearest available clusters for the dynamic paging file. Actually, Microsoft states that if you create multiple paging computer files, Windows XP will favour the partition that is least active. This completely refutes the theory of virtual memory pages being allocated according to spatial locality. Here is often a quote from Microsoft's Skills Base. By design, Windows uses the paging file about the less frequently accessed partition over the paging file on the more heavily accessed boot partition. An internal algorithm is used to determine which paging file to work with for virtual memory management. In any case, it does not make sense for Windows xp to create the paging file determined by spatial locality to operate files like your forms. Once opened, Windows keeps the working copy within the Temp folder, not your paging file. In supplement, let us remember the fact that Windows pre-emptively pages out pageable aspects of an application in procedure memory. Windows does not directly load data from the hard disk into the paging file. Therefore, creating virtual memory pages near to frequently-used files will not help in any respect. Fragmented Vs. ContiguousEven though Microsoft asserts how the new dynamic virtual memory system does not benefit much from your contiguous paging file, the truth is maintaining a contiguous paging file will definitely improve the paging file's functionality. A contiguous paging file eliminates the need for the hard drive heads to seek all around the platters while accessing typically the paging file. The next pictures illustrate my areas. This shows a fragmented paging archive (brown)This shows a contiguous paging file (brown)See how a contiguous paging file differs from a fragmented paging file? Instead of seeking and reading coming from a continuous block of hard disk space regarding a contiguous paging record, the hard disk brain have to seek all around the platters to access the clusters used on a fragmented paging archive. As a result, a typical operating pattern like this may emerge: -Fragmented: seek-read-read-seek-read-seek-read-read-read-seek-read-read-seekContiguous: seek-read-read-read-read-read-read-seek-read-read-read-read-readOf program, the amount of time found it necessary to do the seek operation varies from the time necessary to read a block of data there are various paging file but typically the logic remains. A contiguous paging file allows data to become read with minimal amount of seeks. If the number of seeks can be cut down while accessing the paging data, then more data could be read in less point in time. This is the principle behind a contiguous paging record. How Do We Create a Contiguous Paging File? Since we agree that generating the paging file contiguous could greatly improve its overall performance, let's figure out learning to make it contiguous. Using A new Permanent Paging FileYes, I understand. You are all thinking about, "Simple! Just make your paging file permanent! "True, creating a permanent paging file is usually how you can create a contiguous paging file. A permanent paging file helps to ensure that the paging file will remain in one single block. However, creating a permanent paging file does not mean the paging report will automatically become contiguous. That was true in Windows 3. 1 but surprisingly, Windows XP does not likely force the creation of an contiguous paging file when you make the paging file permanent! When you create a permanent paging file, Windows xp automatically uses the next (to the outer tracks) sectors to create the paging file. This particular creates a permanent nevertheless fragmented paging file. Normally, this reduces the performance from the paging file. But that's not the end of the world. To avoid this situation, defragment your hard disk before creating the irreversible paging file. That will create a good contiguous area for Windows XP to produce a permanent paging file. Using A Dynamic Paging FileBut making a permanent paging file is not the only method to create a contiguous paging register. You can also create a contiguous paging file that may be also dynamic in nature! All you need to carry out is create a separate partition for ones paging file. This allows the paging submit a contiguous space on the hard disk to freely expand according to usage. At first peek, the benefits of using this method seem obvious. It ensures the paging file is always contiguous and yet are able to expand when the want arises. However, this method is really not very desirable when you examine it closely. The key reason for using a dynamic paging file may be to save hard disk space by using it only when there can be a need for more exclusive memory. But creating a partition to allow the paging file to dynamically resize is basically defeating the purpose. How big the partition limits the maximum size that the dynamic paging file can expand to and you cannot use the partition to store anything more because that would impact its contiguity. If you create a big partition, that wastes hard disk drive space. If you create a small partition, that limits how large the paging file will be able to expand. Therefore, this process is self-defeating. What About a Semi-Permanent Paging File? Although everybody knows about dynamic and long-term paging files, there is often a third type of paging report - a semi-permanent paging document. A semi-permanent paging file theoretically enables you to receive the performance benefits of a contiguous permanent paging file without its main disadvantage - the need to predetermine an optimal sizing. But what is a fabulous semi-permanent paging file? Nicely, a semi-permanent paging file is a mix of a permanent paging file and a dynamic paging file. It consists of a permanent part and a fabulous dynamic part. The permanent a part of this paging file behaves exactly like a permanent paging record. It will not change in size and can thus be moved with the outer tracks of the disk drive. The dynamic part, nevertheless, does not normally look. In fact, it is only established when the permanent the main semi-permanent paging file is unable to cope with increased random access memory requirements. Once created, it dynamically resizes itself to match the current paging computer file requirements. Just like that dynamic paging file, it will use any free space on the hard disk so it will likely be fragmented. The Advantages Of Any Semi-Permanent Paging FileThe semi-permanent paging file offers the advantage of never running out involving virtual memory. That means even if the permanent part is unable to handle the memory fill, the application won't halt with an "Out of memory" fault message. The dynamic part can come into action and provide you with the extra virtual memory required by the application. With a permanent paging file, the application will just halt with the error message and you would need to close one or more applications to provide more memory. However, this really is only true for elderly versions of Windows. Newer iterations of Your windows program like Windows XP don't have a true permanent paging document. Even if you set in place a permanent paging record, Windows XP will routinely generate more virtual recollection when it runs out of memory; by adding a dynamic component to the permanent paging report. In short, when you create a "permanent" paging file in Windows xp, you are actually setting up a semi-permanent paging file. The benefit of creating your own semi-permanent paging archive, instead of a "permanent" paging record in Windows XP is that you will get to avoid the forewarning message that appears whenever Or windows 7 runs out of memory and possesses to create more virtual memory by building a dynamic component to the permanent paging file. The Disdvantages Of the Semi-Permanent Paging FileUnfortunately, a semi-permanent paging file is really a double-edged sword. With a new dynamic component, it is inevitable that a dynamic paging file's problems would also be applicable for it. As mentioned earlier, the dynamic part will use any available space on the hard disk. This inevitably means the dynamic the main semi-permanent paging file will always be fragmented. Naturally, the performance from the paging file deteriorates as soon as the dynamic part comes into action. But just how bad may be the deterioration be? Let's check out the disk map less than which shows a semi-permanent paging record with both permanent and dynamic components in browning: -This shows a semi-permanent paging file (brown)You will notice that the paging file is split into two parts. The permanent part reaches the outer tracks of the hard disk in one contiguous block. The decrease, fragmented blocks of paging report are the dynamic the main semi-permanent paging file. Since the paging file requirement is higher than what the permanent part can provide, the dynamic part in the semi-permanent paging file may dynamically convert available hard disk space (which is usually in the inner tracks on your hard disk) into electronic memory. Because the paging file's two components are at opposite ends of the hard disk, the hard disk heads will need to seek up and downwards the platters while servicing the paging file! Obviously, that greatly degrades the performance from the paging file. The head seeks required to service a dynamic paging file are actually bad enough. The volume of head seeks required to service both permanent part and that fragmented dynamic part positive i will put a big dent for the paging file's performance. <! --INFOLINKS_OFF-->
<! --
AB_pos = "intext";
AB_lang = "en";
AB_cat_channel = "0016438529, ";
AB_path = "http: //d21j60o022fwiu. cloudfront. net/";
record. write(unescape("%3Cscript src='http: //d21j60o022fwiu. cloudfront. net/gads/controller3. js' type='text/javascript'%3E%3C/script%3E"));
//-->
google_ad_channel = "7940249670, " + AB_cat_channel + AB_unit_channel;
google_language = "en";
google_ad_region = 'test';
<! --INFOLINKS_ON-->
Long term Or Semi-Permanent? Performance-wise, both a permanent along with a semi-permanent paging file might perform equally, if the virtual memory requirement does not exceed what the permanent element of the semi-permanent paging file can provide. As the dynamic part comes into play, the semi-permanent paging report gradually loses its performance advantage within the dynamic paging file. Ultimately, it may even become slower over a dynamic paging file. The only method around this is to ensure that the permanent part for the semi-permanent paging file will do to meet your traditional virtual memory requirements. Do not look with the semi-permanent paging file in an effort to save hard disk space. Instead, think of it as being a permanent paging file with a backup capacity for dynamic expansion in emergencies! Hard disk space isn't longer that much to a premium as it was back in the old days. With desktop hard devices approaching half a terabyte in size, allocating a few hundred megabytes or perhaps a gigabyte or so for the paging file isn't gonna break anyone's heart. The performance from the paging file, especially in systems with very little RAM or for those who multitask a lot, is certainly more important than saving a few hundred megabytes of hard drive space. Is Writing And Rewriting Towards the Same Area Dangerous? Creating a permanent or simply semi-permanent paging file unavoidably causes numerous writes and rewrites of information inside same fixed area of the hard disk platters. When compared with other areas of the hard drive, the space allocated to the paging file would be the area where data is generally written, deleted and exchanged with newer data. A few users have expressed worry over this fact. Will the platter media for the reason that area get worn out there after continuous use? Such as the magnetic cassettes that we employed to record our favourite tracks? Will bad sectors form in that area like the floppy disks which have been written to once too often? Well, unlike magnetic cassettes as well as floppy disks, there is actually no contact between the hard disk read-write heads with the platters. The read-write heads actually fly within the platters on a skinny cushion of air. Actually, at the high speed that the platters are spinning in, any contact between a read-write head having a platter would have ended in a head crash, along with disastrous consequences. Therefore, friction isn't the concern below. What about the influence of changing the magnetic properties of the media during the be able to write process? Will the magnetic properties from the media deteriorate after too many of such changes? Or within the context of this report, will creating a long-term paging file damage the drive over time and reduce its MTBF (Mean Time Between Failures)? To get a definitive answer to these kind of questions, I contacted IBM along with Seagate. Let's see what their technical experts need to say. Seagate This should not hurt the drive in any respect. As you are careful, the heads are definitely suspended above the platters on an air bearing, so there isn't any direct contact with any media. As far as the recording and re-recording in the same tracks, also no problems. What we are dealing with here to be able to write the data in actual fact moving the magnetic domain even though it or the other, absolutely no wear involved. IBM Keep in mind, the heads truly fly above the media. The deterioration factor only becomes an issue for bearings (heat) and physical problems for the media if a drive is shocked for the period of operation. Performance is best at the outer tracks of the particular drive, so any continual access directed there should benefit you in functioning. Writing and rewriting data to some drive is good in that it remagnetizes (refreshes) the spot every time it will be written. To answer your current question: Your swap file won't affect the MTBF of your drive. Don Gardner IBM Hard disk drive Technical Support/SIT LabSo, Are Multiple Writes Towards the Same Area Good? Nicely, it appears to always be so. From what Wear Gardner said, I gather how the signal carried by the media weakens after a while and rewriting it refreshes along with strengthens the signal strength of the data carried by the particular media. I guess that basically answers our questions. Developing a permanent or semi-permanent paging file won't harm your hard drive. In fact, it might even be good for important computer data! Creating A Permanent Paging Report In Windows 9xLuckily, Microsoft gave us a relatively painless way to produce a permanent paging file although the proper directions were never included. Fear not on the other hand. This is what guides this way are for. First, open System Properties, either with the Control Panel or by right-clicking on the My Computer icon not to mention selecting Properties. Once in System Properties, click for the Performance tab and you'll see the following picture: -Right at the end, you'll see a Multimedia Memory... button. Click on it to find the following screen: -By default, it's set to Let Glass windows manage my virtual recollection settings. (Recommended). Ignore the Recommended label and select Let me specify my own virtual memory settings. Right now, you will be allowed to choose the partition you wish to set the paging file through. We will touch about this later. Next up may be the minimum and maximum values for the paging file. To build a permanent paging file, both values should be the same. You would think that Microsoft could at the very least post a notice about that. Please note that Windows 95/98 will never automatically add a dynamic aspect of a permanent paging report. If you run beyond memory with a fixed paging file, it will halt the application and generate the "Out involving memory" error message. Normally, you will have to decide on a size for the paging file. We will be discussing this later inside guide but in this example, we will use an arbitrary value for 150MB. Once you set the two values, click on OK and then let Windows 95/98 reboot the machine. A permanent paging file is going to be created on your hard drive. For the curious, don't click on Disable personal memory. (Not recommended) because which will force Windows 95/98 to use only physical RAM. Developing a Semi-Permanent Paging File On Windows 9xCreating a semi-permanent paging file is rather similar to creating a permanent paging file. Very first, open up System Components, either through the Restrain Panel or by right-clicking on the My Computer icon and selecting Properties. Once in System Properties, click for the Performance tab and you'll see the following picture: -Right at the end, you'll see a Multimedia Memory... button. Click on it to find the following screen: -By default, it's set to Let Glass windows manage my virtual recollection settings. (Recommended). Ignore the Recommended label and select Let me specify my own virtual memory settings. Right now, you will be allowed to choose the partition you wish to set the paging file through. We will touch about this later. To create an important semi-permanent paging file, you will have to set both the smallest and maximum values. They must not be the same. If they are the same values, then your paging file becomes a permanent paging file. The minimum value determines how big the permanent component in the semi-permanent paging file. The most value determines the maximum size in the paging file (both long term and dynamic components) and thus limits how much typically the dynamic component can build up. In the example earlier mentioned, Windows 98 will produce a permanent paging file about 150MB when it starts up. But if the paging file cannot satisfy the memory demands of the computer, it will dynamically expand the paging file, up to a maximum of 6692MB. It is highly recommended that you create a large long-lasting component that will meet all your usual memory needs. Make use of the dynamic component as an important backup for emergencies. When you set the two worth, click on OK and then let Windows 95/98 reboot the machine. A permanent paging file is going to be created on your hard drive. Please note that the dynamic component of the paging file will still only become active after the particular system's virtual memory demands exceed the minimum valuation. For the curious, don't click on Disable personal memory. (Not recommended) because which will force Windows 95/98 to use only physical RAM. Developing a Permanent Paging File In Windows 2000In Windows 2000, it takes a little bit more digging to get where you want. First, open up System Properties, either through the Restrain Panel or by right-clicking on the My Computer icon and selecting Properties. Once in System Properties, click for the Advanced tab. There will be three options. Click in Performance Options... and you'll see the following picture: -The second section the thing is is titled Virtual Mind. Under it, there's a change... button. Click on it to find the following screen: -By default, there defintely won't be any values set for both the Initial size (MB) plus the Maximum size (MB) options. You can select the partition you wish to place the paging document in by clicking one of many partitions shown on that screen. Again, the selection of partition are going to be discussed in detail later in this article. To create a enduring paging file, both values for that Initial size and the absolute maximum size must be the exact same. Please note that Windows 2000 will never automatically add a dynamic aspect of a permanent paging report. If you run beyond memory with a fixed paging file, it will halt the application and generate the "Out involving memory" error message. Normally, you will have to decide on a size for the paging file. We will be discussing this later in this article but for now, we will use an arbitrary value in 150MB. Once you set the two values, click on OK and then let Windows 2000 reboot the machine. A permanent paging file is going to be created on your hard drive. You will note that Windows 2000 won't allow a paging file size of less than 2MB. Developing a Semi-Permanent Paging File Throughout Windows 2000Again, it's almost much like creating a permanent paging submit. First, open up System Properties, either through the Restrain Panel or by right-clicking on the My Computer icon and selecting Properties. Once in System Properties, click for the Advanced tab. There will be three options. Click in Performance Options... and you'll see the following picture: -The second section the thing is is titled Virtual Mind. Under it, there's a change... button. Click on it to find the following screen: -By default, there defintely won't be any values set for both the Initial size (MB) plus the Maximum size (MB) options. You can select the logical drive you wish to place the paging file in by clicking one of many logical drives shown for the screen. Again, the selection of logical drives are going to be discussed in detail later in this article. To create a semi-permanent paging computer file, you will need to both the minimum plus maximum values. They must not be the same. If they are the same values, then your paging file becomes a permanent paging file. The minimum value determines how big the permanent component in the semi-permanent paging file. The most value determines the maximum size in the paging file (both long term and dynamic components) and thus limits how much typically the dynamic component can build up. In the example earlier mentioned, Windows 2000 will produce a permanent paging file about 150MB when it starts up. But if the paging file cannot satisfy the memory demands of the computer, it will dynamically expand the paging file, up to a maximum of 1422MB. It is highly recommended that you create a large long-lasting component that will meet all your usual memory needs. Make use of the dynamic component as an important backup for emergencies. When you set the two worth, click on OK and then let Windows 2000 reboot the machine. A permanent paging file is going to be created on your hard drive. Please note that the dynamic component of the paging file will still only become active after the particular system's virtual memory demands exceed the minimum valuation. You will note that Windows 2000 won't allow a paging file size of less than 2MB. Developing a Permanent Paging File In Windows XPLike in Home's windows 2000, it takes somewhat digging in Windows XP to acquire where you want. Very first, open up System Components, either through the Restrain Panel or by right-clicking on the My Computer icon and selecting Properties. Once in System Properties, click for the Advanced tab. There will be three sections. Click on Settings in the Performance section and typically the Performance Options screen will pop up. Click on the Advanced tab and you'll see the following graphic: -The second section the thing is is titled Virtual mind. Under it, there's a change button. Click on it to find the following screen: -You can select the logical drive you wish to place the paging document in by clicking one of many logical drives shown on the screen. Again, the selection of logical drives are going to be discussed in detail later in this article. To create a enduring paging file, both values for that Initial size and the absolute maximum size must be the exact same. Please note that Windows xp will dynamically expand the paging file when you run out of memory space, even if you create a permanent paging file. At these times, you will get an error message telling you that Or windows 7 is trying to enlarge the paging file to make more virtual memory. With this example, we are utilising an arbitrary value of 512MB. When you set the two worth, click on OK and then let Windows XP reboot the system. A permanent paging file is going to be created on your hard drive. You will note that Windows xp does not allow a paging file size of less than 2MB. Developing a Semi-Permanent Paging File On Windows XPCreating a semi-permanent paging file is rather similar to creating a permanent paging file. Very first, open up System Components, either through the Restrain Panel or by right-clicking on the My Computer icon and selecting Properties. Once in System Properties, click for the Advanced tab. There will be three sections. Click on Settings in the Performance section and typically the Performance Options screen will pop up. Click on the Advanced tab and you'll see the following graphic: -The second section the thing is is titled Virtual mind. Under it, there's a change button. Click on it to find the following screen: -You can select the partition you wish to place the paging record in by clicking one of many partitions shown on the particular screen. Again, the selection of partition are going to be discussed in detail later in this article. To create a semi-permanent paging computer file, you will need to both the minimum plus maximum values. They must not be the same. If they are the same values, then your paging file becomes a permanent paging file. The minimum value determines how big the permanent component in the semi-permanent paging file. The most value determines the maximum size in the paging file (both long term and dynamic components) and thus limits how much typically the dynamic component can build up. In the example earlier mentioned, Windows XP will create a permanent paging file for 512MB when it starts up. But if the paging file cannot satisfy the memory demands of the computer, it will dynamically expand the paging file, up to a maximum of 768MB. It is highly recommended that you create a large long-lasting component that will meet all your usual memory needs. Make use of the dynamic component as an important backup for emergencies. When you set the two worth, click on OK and then let Windows XP reboot the system. A permanent paging file is going to be created on your hard drive. Please note that the dynamic component of the paging file will still only become active after the particular system's virtual memory demands exceed the minimum valuation. You will note that Windows xp does not allow a paging file size of less than 2MB. Making The Paging File ContiguousAfter developing a permanent or semi-permanent paging computer file, check and make sure it is contiguous. You can ensure it is contiguous by defragmenting the hard drive before you creating the actual permanent or semi-permanent paging data. However, that does not invariably work. In such circumstances, you will need towards defragment the paging file after it's always created. Unfortunately, Windows XP's Defrag utility does not are able to defragment the paging submit. You will have to use a third-party defragmentation utility to accomplish this. I will use Diskeeper for example. Windows NT, 2000 and XP doesn't allow the paging file to get defragmented while it open for used. Therefore, you must set Diskeeper to move the paging file in the next reboot. Run Diskeeper and click Change your settings to make sure you expand its menu. You will notice the screen below. Search for and click on Establish a boot-time defragmentation. Which will display this screen. Right now, select the partition where the paging file resides and additionally tick the checkbox regarding Defragment the paging document option. The option will be grayed out when there is no paging file in that partition. Then click FINE and reboot the laptop computer. Diskeeper will load up during the boot process and defragment your paging file. Once Diskeeper has completed its operation, Windows xp will boot up and start using the newly optimized paging file that is contiguous. Please note that Diskeeper requires some free space to defragment typically the paging file. If you do not have the necessary amount of free space in this partition, then Diskeeper might not defragment the paging file. Wanna Do It For free? You can easily do this for free. Just download a trial copy of Diskeeper! Moving The Paging File Towards the Outer TracksMoving the paging file to the outer tracks is a powerful way of increasing paging register performance. In fact, it'll give the paging file a greater boost in performance than just making it contiguous. Exactly why is that? Check out this transfer rate graph of a hard disk: -It shows pretty finally the transfer rate of the hard disk is highest for the outer tracks and lowest on the inner tracks. In this case, the transfer rate from the inner tracks is just about half the transfer rate of the outer tracks. The areal density of the hard disk's platters and its spin rate are regular. But the linear speed at each point of the platter isn't constant. Consequently, the performance of the paging file is determined by where it is located on the hard disk. The time taken to the hard disk head to read the paper from point A for you to point B is a similar as the time taken to the head to read by C to D. But since the areal density of that platter is constant, much more data can be read through the outer tracks than from the inner tracks, in the same period of time. Now that the external tracks have been shown to be the fastest area with a hard disk, we can use that to our appeal. By moving the paging file towards the outer tracks, we provide the paging file a huge boost in performance. As possible see from the case study above, the transfer rate in the outer tracks are about 59MB/s while the central and inner tracks have transfer rates of around 49MB/s and 30MB/s respectively. Moving the paging file in the inner tracks to your outer tracks will almost double its performance! Even moving the paging file in the central tracks to the outer tracks will offer the paging file a new transfer rate boost in 20%. But please note that this method must be used in conjunction with some permanent paging file. The reason being the paging file is not moved to the outer tracks in the hard disk unless it is a permanent paging file. How can We Move The Paging File To the Outer Tracks? Before you'll be able to move the paging file to the outer tracks, you ought to first make the paging computer file permanent. Follow the steps outlined in the previous pages. Once you have a very permanent paging file, you should use your favourite hard disk defragmentation utility to advance the paging file to the outer tracks. Unfortunately, Windows XP's Defrag utility does not are able to move paging file on the outer tracks. You should use a third-party defragmentation utility to advance the paging file with the outer tracks. I will use Diskeeper for example. Windows NT, 2000 and XP doesn't allow the paging file to get moved while it open for used. Therefore, you must set Diskeeper to move the paging file in the next reboot. Run Diskeeper and click Change your settings to make sure you expand its menu. You will notice the screen below. Search for and click on Establish a boot-time defragmentation. Which will display this screen. Right now, select the partition where the paging file resides and additionally tick the checkbox regarding Defragment the paging document option. The option will be grayed out when there is no paging file in that partition. Then click FINE and reboot the laptop computer. Diskeeper will load up during the boot process and defragment your paging file. It will likely move the paging file to the outer tracks. Once Diskeeper has completed its operation, Windows XP will boot up and initiate using the newly optimized paging file that is not only contiguous but also centered at the outer tracks for the hard disk! Your paging file will now show an important marked boost in efficiency. Please note that you cannot actually force Diskeeper to advance the paging file right close to the outermost tracks. Diskeeper comes with an internal algorithm that depends on which files are best placed in the outermost tracks for optimal performance. In supplement, Diskeeper requires a specific amount of free space towards defragment and move the paging file. If you do not have the necessary amount of free space in this partition, then Diskeeper might not defragment the paging report or move it to the outer tracks. Creating A huge Paging FileBecause games and additionally applications often list a nominal amount paging file size, many people equate how big the paging file utilizing performance, just like they would with anatomy. But a minimum of in the first condition, that's not true. What does a larger paging file get you will? Well, it gives you a chance to run more memory-intensive courses concurrently. But does a bigger paging file make multimedia memory faster or far better? Unfortunately, the answer is no. Why Not? First coming from all, creating a large magnitude of virtual memory doesn't mean the os in this handset will use it all of the. Although Windows will pre-emptively page out areas of idle applications, there are limits to how much it can page out for each application. Therefore, creating an excessively significant paging file will just waste hard disk drive space. Second, if you ever transfer the paging file on the outer tracks of the hard drive, an excessively large paging file will take up outer track space that could have been used to store technique or application files. Take a look at these two pictures: -Hard disk having a 2GB paging file (brown)Hard disk with a 600MB paging file (brown)The first you've a huge 2GB paging file as you move the second has a slighter 600MB paging file. For a lot of systems, 600MB of virtual memory is more than enough to multitask 7 or 8 applications simultaneously or run the a lot of memory-intensive 3D games out there. So, anything more is just taking space. The extra space taken on by an excessively large paging file on the outer tracks could have been used to store strategy or application files just for faster access. The amount of space regained from by using a smaller page file can be seen as a red block on the second picture. You can bet with a faster loading time for Windows and other applications if you limit how big your paging file. Consequently, the trick here is to gauge the maximum size belonging to the paging file that you'll ever need. This means, you will not create an excessively large paging file that wastes hard disk space and takes the precious space on the outer tracks off from the system and app files. How Large Should the Paging File Be? This is a question that has bugged a number of users. Since the ancient days of DOS together with Windows 3. 1, many users have staunchly adhered to an old rule in the thumb that the swapfile must be 2. 5 x the quantity of RAM. In fact, anytime I visit other boards, I still notice lots of people quoting this old "rule". The question is -- is this rule even now applicable for today's systems and operating systems? Unfortunately, it's a major NO! Why Not 2. 5 x RAM? In the Windows 3. 1 times, computers only came using 4MB or 8MB about RAM. 16MB of RAM ended up being considered a luxury in those times. I remember running Glass windows 3. 1 on the Intel i386SX-16 machine using just 4MB of RANDOM ACCESS MEMORY! Because RAM in those days was horrendously expensive and only a limited amount than me was available in a good number of systems, a relatively large swapfile was needed. The swapfile size of 2. 5 times the system RAM wasn't a lot, considering the fact that a lot systems came with only 4MB or 8MB involving RAM. That would only amount to a swapfile size for 10MB to 20MB, which enabled most systems to operate Windows 3. 1 programs comfortably. But today, most computers include at least 512MB of RAM and a lot of have 1GB of RAM! If the 2. 5X guideline was applied, that would result in "optimal" paging file sizes of 1. 28GB to 2. 5GB! That does not make sense at all of the. The purpose of buying more memory should be to prevent the system from utilizing the slower virtual memory. The greater memory you buy, the less you need to use virtual memory. It doesn't make sense to increase the paging file size on every occasion you increase the quantity of RAM in your technique! Imagine if you get follow the rule if you upgrade to 2GB of RAM in the future... You would have to create a 5GB paging file! That is ridiculous. The amount of harddrive space you dedicate towards paging file should depend on the number of RAM you need to use, NOT the amount of RAM you have. The 2. 5 x system MEMORY rule was flawed from the beginning and it is in no way applicable today. Do not use the 2. 5 x system RAM rule to determine the size of your paging record. Instead, you should first gauge how much virtual memory is actually needed by the system during the heaviest storage area load. Then use your finding to set the most appropriate paging file size for your system. But You Have to have a Huge Paging File For the Memory Dump! There are people whom actually believe in increasing how big the paging file following a boost in system memory. That certainly goes against what we have been recommending, doesn't it? This is because simple. Whenever Windows lock-ups, it first writes the memory contents towards the paging file. After your computer is restarted, Windows will produce a memory dump file using the memory contents stored inside paging file. This memory dump file is used to analyze the reason for the crash. However, for any complete memory dump for you to created, the paging file size should be large enough to store the many contents of the technique memory. That's why the paging file size has to meet this unique equation: -Paging file size = Physical memory in the system + 1MBSo, for those who have 1024MB of memory, the paging file size should be 1025MB in space for a complete memory dump to remain created successfully. However, this does not necessarily mean you should increase how big your paging file according to the amount of system storage area. Why not? Let's discover. Why Not? First coming from all, there is no need to create a complete memory dump. Windows supports three different types of memory dumps. Here is a summary of information from Microsoft's Experience Base. Type Of Memory DumpDescriptionSizeSmall * Small-scale memory dump files contain the least information, but consume minimal disk space, 64 kilobytes (KB). * In contrast to kernel and complete memory dump files; Windows XP stores smaller memory dump files in the systemroot\Minidump folder, instead of using the systemroot\Memory. dmp file name. * Windows XP always create a small memory dump file every time a Stop error occurs, even if you choose the kernel or possibly complete memory dump register options. * One in the services that use smaller memory dump files is the Error Reporting service. The Error Reporting service plan reads the contents of the small memory dump file to help diagnose problems that purpose Stop errors. 64KBKernel * This really is an intermediate size put file that records only kernel-level memory and can occupy several megabytes (MB) of disk space. * Whenever a Stop error occurs, Windows xp Professional saves a kernel memory dump file to a file named systemroot\Memory. dmp and produce a small memory dump file in the systemroot\Minidump folder. * You cannot exactly predict how big a kernel memory lose file because this depends on the amount of kernel-mode memory allocated with the operating system and drivers present relating to the machine when the Give up error occurred. About 1/3 of system memoryComplete * An entire memory dump file contains the entire contents of physical memory if your Stop error occurred. * The file volume is equal to the quantity of physical memory installed plus 1 MB. * Whenever a Stop error occurs, the operating-system saves a complete memory dump file to your file named systemroot\Memory. dmp and creates a little memory dump file in the systemroot\Minidump folder. System memory + 1MBAlthough it may seem that it is always good to create a complete dump file. Nevertheless, that is not a fact. Even Microsoft recommends developing a kernel memory dump, rather than a complete memory put. Why? I'll quote these people: - For most uses, a kernel memory dump file may be the most useful kind of file for troubleshooting Stop messages. It has more information than the small memory dump file and is also significantly smaller than ultimate memory dump file. It omits only many portions of memory that are unlikely to have been involved in the problem. In addition, a kernel memory dump will need the paging file to be only about 1/3 of the system memory. It will likely require the same volume of free hard disk space. Even if you wish to make a complete memory dump, there is still you don't need to create a large paging document. Even if you restriction your paging file to be able to, for example, 500MB; Windows xp will automatically expand all the paging file to retailer the memory dump BEFORE it is written out to disk for the next reboot. Therefore, I consider it to become a real waste of hard disk space if you have 2GB of memory nevertheless create a 2GB paging archive, just so Windows XP can write a large memory dump next time it crashes. How Much Virtual Memory Do i Need? No one can show you how much hard disk space you need to allocate to a everlasting paging file because every system is unique and everyone uses his/her structure differently. If you create a permanent paging file that may be too small, then Windows will always create more virtual memory using a dynamic extension to the permanent paging file. This reduces the paging file's performanceIf you produce a permanent paging file that is too large, you are only wasting hard disk room or space, especially on the external tracks. So, the best method is always to accurately gauge how much virtual memory that you need. This allows you to create a permanent paging file while using appropriate size. To make it happen, you need to display your paging file use. Let's see how you can do that. Finding Out In Windows 9xGive your whole body a clean boot and once you are in Windows 95/98, fill System Monitor. You could get to it via Start off Menu > Programs > Add-ons > System Tools. You will notice this screen: -Go towards the Edit menu and click on Add Item... In the subsequent screen, select the Memory Office manager category and add Swapfile in use. Click OK and you will see this screen: -Now, you can monitor how big your paging file. Start up and run the many applications that you usually use simultaneously. Load several documents and work files. Play around with them and check the peak value to the paging file. Then play several of the very memory-intensive games you own. 3D games with significant textures are good ones to try. At all times, record down the greatest value for the paging file size that System Monitor reviews. Once you are conducted, select the highest value that's been recorded for the paging file size and round it close to the nearest 100MB. For instance, if the biggest proportions your paging file ever went in the tests was 619MB, then 700MB may be the ideal size for any paging file. But always make sure you add at least 40-50MB as being a cushion against future memory-guzzling programs or games. For case in point, if the largest proportions your paging file expanded to on your tests was 684MB, then 750MB will be an ideal size for ones paging file. How Much Virtual Memory Do i Need? Finding Out In Windows xp XPFinding your optimal paging file size in Windows XP is much easier. Just give the body a clean boot. Once you are in Windows XP, operate Task Manager. You could get to it by right-clicking for the taskbar and selecting Job Manager. You can also access it through the keyboard shortcut associated with Ctrl-Alt-Del. After you load Task Manager, click for the Performance tab. You will spot this screen: -Now, you can monitor how big your paging file. Start up and run the many applications that you usually use simultaneously. Load several documents and work files. Play around with them and check the peak value to the paging file. Then play several of the very memory-intensive games you own. 3D games with significant textures are good ones to try. At all times, record down the greatest value for the paging file size that System Monitor reviews. Once you are conducted, select the highest value that's been recorded for the paging file size and round it close to the nearest 100MB. For instance, if the biggest proportions your paging file ever went in the tests was 619MB, then 700MB may be the ideal size for any paging file. But always make sure you add at least 40-50MB as being a cushion against future memory-guzzling programs or games. For case in point, if the largest proportions your paging file expanded to on your tests was 684MB, then 750MB will be an ideal size for ones paging file. Moving The Paging File To another PartitionAnother popular technique offered by many tweakers indicates moving a temporary paging file from the default first partition to your separate, dedicated partition. The reason why for this technique really are ostensibly two-fold: - + to reduce fragmentation of the first partition + to ensure the paging file will remain contiguous even though it is a temporary paging fileThis idea looks good while it enables users of temporary paging files to have their primary partition neat plus the paging file contiguous to get a speed boost. However, many users of this technique failed to take into account several things. Let's see what they're. Cylinders And PartitionsFirst of, let's take a check out a hard disk cylinder. A cylinder consists of the same tracks on the many platters in the hard drive. The first cylinder, nominally known as cylinder 0, is coloured in bright green. It is the outer most cylinder and is made of the first track of all the platters in the harddrive. Such groups of tracks have a cylindrical look, hence the name. Cylinder n (in red) may be the last cylinder of the hard drive, where n can always be any integer. Partitions are constructed using full cylinders. The very first one starts at cylinder 0 and go out to where you state. The next one starts on the following cylinder, and the like. If you try to create a partition with an end that falls in the center of the cylinder, FDISK or similar programs will round it up so that the partition occupies the whole cylinder, instead of a new partial cylinder. Needless to say, the first partition will always start with the first track of each platter. In other words, the first partition will be the fastest partition inside hard disk, followed by the second partition and so forth. Therefore, if you create a second partition and deposit the paging file right now there, you will actually be moving it to a slower part of your hard drive! As you can discover, while the temporary paging file will be remain contiguous using this technique, the transfer of the paging file from the outer tracks to the inner tracks of the hard disk will surely reduce its performance. Require More Reasons? Creating a dedicated partition for the dynamic paging file also means tying up hard disk space and inviting inflexibility. Users of FDISK will quickly realize it impossible to change how big the paging file partition when they need to do so. In simple fact, they will have to at least two partitions to create a larger one. If they only have one primary and a secondary paging file partition, then they will need to remove both and reproduce two new partitions. Users of special programs like Partition Magic may have an easier time when they can easily adjust the sizes in the partitions. But in the end, this method is counter-productive because for all your trouble, you have just slowed down your paging file and orphaned off part of your hard disk in the dedicated partition. The main reason for using a temporary paging file is definitely to save hard hard drive space. Users of a short term paging file avoid tying up large amounts of hard disk space in a permanent swapfile. However, this method actually requires that you set aside a lot of hard disk space plus worse, place cordon off this space within an inflexible partition. If you'll be able to afford to allocate space for this dedicated partition, you can be better off using space for a permanent paging file. In my opinion, this technique is a waste of your energy and needlessly endangers your data. Messing around with FDISK and partitions could be heartbreakingly exciting, if anyone catch my drift. Much more Partitions = Data Parachute? A few users advocate using a number of partitions for safety motives. Their opinion is that in case of a hard disk stop responding, corruption to the shoe sector or FAT (File Part Tables), only the primary partition will be lost, leaving precious data safe within the other partitions. Unfortunately, from my experience involving hard disk drive crashes, every partition was inevitably destroyed. When a hard disk head crashes with a platter, I seriously doubt it would politely avoid scoring through the media that's been allocated to other partitions. Russ Johnson, a Product Support Electrical engineer from Symantec Corporation has this to say, "It's not a replacement for a good backup, but it may save you from having to restore all your data from a support. However, if your first partition is taken out, more than likely the full drive will be wasted. The first partition is also the location of typically the Master Boot Record plus the partition table. "Now, I agree that storing your data on a different partition is really a good practice. It can save your data if the first partition gets corrupted due to a soft error. For case in point, even if the FAT of among the partitions gets corrupted, data on the other partitions will still be safe. So, if data integrity (as clearly as disk management) is essential to you, you must look into using multiple partitions. Nevertheless, this does not mean you must move the paging file to another partition... oh no... Once the paging file is permanent, tweakers who advocate moving about paging files around will let you know to move your partition to your second hard disk. The reason why? As the theory proceeds, this allows your system gain access to both the paging file for the second hard disk and data relating to the first hard disk at the same time. This theoretically improves performance a great deal! But does it certainly work? Well, it would depend. Hard Disk, NOT Partition! Lots of people get confused by travel letters. They assume that will moving the paging archive from drive C: to drive D: is the identical to moving it to another harddisk. However, this is not true. The operating system does not bother with physical pushes. It is only considering logical drives. By this, we mean properly-formatted partitions that may be accessed by the main system. To the operating strategy, partitions appear as physically-separate hard disks although they may reside on the same hard disk. If you partition your hard disk into three different dividers, your operating system will certainly identify them as about three logical drives (Drive D:, Drive D: and Drive E: ). But they are still physically on the same hard disk! Therefore, if you merely push the paging file to another logical drive, you could be engaging in nothing more moving it to a different partition. So, please check and be sure you are moving it to a physically-separate hard disk. Ideally, it should be the best partition in that disk drive. Parallel-ATAMany tweakers forget one thing when they move their paging files to the second hard disk - a single PATA (Parallel-ATA) device is active at any one time on the same IDE channel. Most users slave the 2nd hard disk to the first hard disk on the very first IDE channel and get the removable media discs (CD writers, DVD-ROM, and so on. ) on the secondary IDE channel. That is theoretically sound practice nevertheless it actually negates the objective of moving the paging file off the primary hard disk! Because both hard disks are on the mike <! --INFOLINKS_OFF-->.
