•
•
•
•
What is DaniWeb IT Discussion Community?
You're currently browsing the Windows tips 'n' tweaks section within the Tech Talk category of DaniWeb, a massive community of 403,504 software developers, web developers, Internet marketers, and tech gurus who are all enthusiastic about making contacts, networking, and learning from each other. In fact, there are 4,208 IT professionals currently interacting right now! Registration is free, only takes a minute and lets you enjoy all of the interactive features of the site.
Please support our Windows tips 'n' tweaks advertiser: Programming Forums
Views: 9843 | Replies: 22
![]() |
•
•
Join Date: Dec 2004
Location: Lincoln Park, Michigan
Posts: 1,744
Reputation:
Rep Power: 7
Solved Threads: 108
(Read Edit To Prior Post)
•
•
•
•
In spite of the name 'virtual memory' the paging file is really just a chunk of reserved hard drive space where data may be written and retrieved as needed. Since the paging file and operating system files are by default located on the same drive, concurrent access to both locations is impossible. One or the other has to wait, slowing down overall system performance...
Last edited by Comatose : Aug 28th, 2006 at 11:43 pm.
•
•
Join Date: Dec 2004
Location: Lincoln Park, Michigan
Posts: 1,744
Reputation:
Rep Power: 7
Solved Threads: 108
•
•
Join Date: Feb 2007
Posts: 6
Reputation:
Rep Power: 0
Solved Threads: 0
The reduction in performance is something you will probably never notice, Keep in mind every time you run an application for the first time windows is creating a .pf file, When the max of 128 .pf files it starts removing the older/unused ones. Which means when you run an app that you haven't ran for a while it will once again recreate the .pf file., So clearing out your prefetch is not going to slow down your computer as detrimentally as some are making it sound.
Im not sure who has ever had this take up 100% of the processor unless its norton or mcafee trying to scan something (choke choke..)
One thing you should definitely clear out is your temp folder
c:\documents and settings\username\local settings\Temp
It is not uncommon that spy ware will run entirely out of the temp folder because it is not automatically cleared like it should be considering its called a temp folder..
Im not sure who has ever had this take up 100% of the processor unless its norton or mcafee trying to scan something (choke choke..)
One thing you should definitely clear out is your temp folder
c:\documents and settings\username\local settings\Temp
It is not uncommon that spy ware will run entirely out of the temp folder because it is not automatically cleared like it should be considering its called a temp folder..
•
•
Join Date: Jan 2005
Posts: 24
Reputation:
Rep Power: 4
Solved Threads: 0
•
•
•
•
The reduction in performance is something you will probably never notice, Keep in mind every time you run an application for the first time windows is creating a .pf file, When the max of 128 .pf files it starts removing the older/unused ones. Which means when you run an app that you haven't ran for a while it will once again recreate the .pf file., So clearing out your prefetch is not going to slow down your computer as detrimentally as some are making it sound.
Im not sure who has ever had this take up 100% of the processor unless its norton or mcafee trying to scan something (choke choke..)
One thing you should definitely clear out is your temp folder
c:\documents and settings\username\local settings\Temp
It is not uncommon that spy ware will run entirely out of the temp folder because it is not automatically cleared like it should be considering its called a temp folder..
Don't state nonsense. If Windows now boots in 35 seconds and you delete the prefetch files and it then boots in 60 seconds, you will not notice this? If an application loads in 10 seconds but you delete the prefetch files and it then loads in 20 seconds, you will not notice this? The larger the application and the slower your computer the more "you will notice it". How much you will "notice" is dependent on MANY factors, including the speed of your HD, the HD interface speed, the amount of RAM in your system and the application loading. The fact remains you want your applications to load as quickly as possible and there is NEVER any reason to clean the prefetch folder.
Correction, when the 128 limit is reached, all but the most used 32 prefetch files are flushed. This is based on information stored in the prefetch files. Thus these 32 most used application's performance would NEVER be affected. When you manually delete the folder, you delete ALL of them including the 32 that Windows would leave for your common applications. And yes the file is recreated but BEFORE it is recreated the application loads SLOWER! Why? Because you felt like cleaning the folder for no reason! Leave the folder alone and let windows take care of it.
Clearing out the temp folder is not a way to clean spyware. All modern malware is very resilient to being removed, especially by simplistic suggestions like this. You need to run scans to make sure you are clean. All cleaning the temp files does is increase available disk space.
Last edited by Mastertech : Jul 4th, 2007 at 9:08 pm.
•
•
Join Date: Feb 2007
Posts: 6
Reputation:
Rep Power: 0
Solved Threads: 0
Do you honestly think there is an increase in wait of up to 30 seconds at boot time? The only way you would notice a boot time increase that much by clearing out your prefetch would be if you have alot of extra apps starting up.. Yeah, If you have 15 apps starting up every time you boot your computer, you will notice a difference when you clear your prefetch folder, but most people that are looking for performance don't have alot of startup items, and the boot time would not increase like you say.. I personally have the same boot time results after cleaning out my prefetch folder. I suppose if you have a slower machine or alot of startup apps this would slow down your boot time, However if you run your machine optimally with as little to start with as possible it doesn't matter if your prefetch is full or empty.
I did not state that cleaning out your temp folder is a solution to your spyware problems, I said that it is not uncommon that spyware will run entirely out of the temp folder, While this is true, there is also spyware that runs under the windows, system32, dllcache, restore and various other folder, but I am not going to give advice to people as to start deleting crap out of those folders.. I have seen various cases where a simple piece of spyware is running under the temp folder, commonly with some long name like asfd98uwer.exe.. So, In the case of cleaning the temp folder, yeah, of course it increases disk space, but it also can make a difference on startup time, as the spyware that was running out of the temp folder is no longer loaded, and of course this is not a fix all solution, but for a novice it is a place to start, for someone like me it is the first thing I clear, and the prefetch too, cuz I heard some people are sensitive about that folder..
Truth of the matter is in most cases, if you make sure explorer is loading as your shell, there are no bad bho's, you clear your temp, and clear out any suspicious startup items in safe mode, a good amount of times (not all of course) This will fix the problem. If you have something a little more difficult, like spyaxe (isnt that fun) you will need to do more, but there fortunately hasn't been too much spyware that is designed that well.
I did not state that cleaning out your temp folder is a solution to your spyware problems, I said that it is not uncommon that spyware will run entirely out of the temp folder, While this is true, there is also spyware that runs under the windows, system32, dllcache, restore and various other folder, but I am not going to give advice to people as to start deleting crap out of those folders.. I have seen various cases where a simple piece of spyware is running under the temp folder, commonly with some long name like asfd98uwer.exe.. So, In the case of cleaning the temp folder, yeah, of course it increases disk space, but it also can make a difference on startup time, as the spyware that was running out of the temp folder is no longer loaded, and of course this is not a fix all solution, but for a novice it is a place to start, for someone like me it is the first thing I clear, and the prefetch too, cuz I heard some people are sensitive about that folder..
Truth of the matter is in most cases, if you make sure explorer is loading as your shell, there are no bad bho's, you clear your temp, and clear out any suspicious startup items in safe mode, a good amount of times (not all of course) This will fix the problem. If you have something a little more difficult, like spyaxe (isnt that fun) you will need to do more, but there fortunately hasn't been too much spyware that is designed that well.
•
•
•
•
Don't state nonsense. If Windows now boots in 35 seconds and you delete the prefetch files and it then boots in 60 seconds, you will not notice this? If an application loads in 10 seconds but you delete the prefetch files and it then loads in 20 seconds, you will not notice this? The larger the application and the slower your computer the more "you will notice it". How much you will "notice" is dependent on MANY factors, including the speed of your HD, the HD interface speed, the amount of RAM in your system and the application loading. The fact remains you want your applications to load as quickly as possible and there is NEVER any reason to clean the prefetch folder.
Correction, when the 128 limit is reached, all but the most used 32 prefetch files are flushed. This is based on information stored in the prefetch files. Thus these 32 most used application's performance would NEVER be affected. When you manually delete the folder, you delete ALL of them including the 32 that Windows would leave for your common applications. And yes the file is recreated but BEFORE it is recreated the application loads SLOWER! Why? Because you felt like cleaning the folder for no reason! Leave the folder alone and let windows take care of it.
Clearing out the temp folder is not a way to clean spyware. All modern malware is very resilient to being removed, especially by simplistic suggestions like this. You need to run scans to make sure you are clean. All cleaning the temp files does is increase available disk space.
•
•
Join Date: Apr 2005
Location: Old Hampshire, Old England (LOL)
Posts: 11,937
Reputation:
Rep Power: 30
Solved Threads: 268
the 30 seconds thing is pretty true as prefetch loads common parts of the XP shell, kernel, services and drivers.
TRY MY SUGGESTIONS AT YOUR OWN RISK!
james.bennet1@ntlworld.com
james.bennet1@ntlworld.com
•
•
Join Date: Jan 2005
Posts: 24
Reputation:
Rep Power: 4
Solved Threads: 0
Does anyone know how this works? Listen Prefetching does not load ANYTHING that is not already being loaded. What it does is OPTIMALLY load what is ALREADY being loaded. Prefetching is an optimization PROCESS. It is not something that loads more things!!!! So if file A, B and C load during startup with Prefetching enabled A, B and C still load at startup (Nothing more) but they simply load FASTER!
CMN - You HAVE NO IDEA WHAT YOU ARE TALKING ABOUT. Even on slow systems you boot times are improved with Prefetching, irrelevant to how many apps you have loading at startup. The exact amount of time that is changed varies based on MANY FACTORS but it is without a doubt SLOWER when you clean the folder = FACT. I work for a system OEM, have tested this on hundreds of machines of all varying speeds and have consulted fully on this issue with the Microsoft Client Performance Team. You Personally do not know how to properly test this even remotely. Go read up on this before you misinform more people, There is NO REASON TO CLEAN THE PREFETCH FOLDER PERIOD:
Here is some reference material:
Kernel Enhancements for Windows XP
Windows XP: Kernel Improvements Create a More Robust, Powerful, and Scalable OS
Benchmarking on Windows XP
One more time: do not clean out your Prefetch folder!
Tip of the day: Don’t clean out the Prefetch folder
Debunking yet another bogus Windows tip
Beware of Bogus XP Advice
Misinformation and the The Prefetch Flag
Anyone claiming any performance improvement from adjusting, tweaking, optimizing, cleaning or changing anything in relation to the default prefetcher registry settings, folder or files has either never tested it or improperly tested it. You will not find any fully documented, reproduceable testing in relation to these "performance" claims anywhere on the Internet
Testing Boot Prefetching:
Setup Requirements - Before beginning with testing you must confirm the following:
- Windows XP/Vista must have been cleanly installed from a non-nlite, lawfully owned, original installation CD.
- Your computer hardware must be in proper working order and properly configured.
- Your computer must not be overclocked.
- Your computer must not be infected with any Malware, Spyware or Viruses.
- Your computer must have a Hard Disk Drive, not a Solid State (flash-based) Drive.
- Prefetching must be enabled and working properly (it is by default).
Failure to meet all of these requirements will result in inaccurate timing results.
The following on a default installation of Windows will be done by Windows automatically at system idle times and roughly every 3 days.
1. Make sure the following Services are set to Automatic:
-Task Scheduler (It is by default but many people and bad tweaking programs disable it)
-COM+ Event System
2. Make sure Prefetching is properly enabled (it is by default) run the Prefetcher Fix: http://mywebpages.comcast.net/Suppor...XP.html#Tweaks
3. Reboot and make sure in the \Windows\Prefetch folder the following files are present:
-NTOSBOOT-B00DFAAD.PF
-Layout.ini
4. Reboot Windows and wait one full minute at the desktop so Windows can write the NTOSBOOT-B00DFAAD.PF file. Reboot Windows a second time and wait again 1 full minute. DO NOT install or change anything that would load during Windows Startup during any of this.
5. Download and install Bootvis. (Without using Bootvis you would have to wait 3 or more days for this optimization to happen automatically.) http://www.soft32.com/download_19687.html
6. In the menu go to "Trace" and select "Optimize System" and Reboot. This time when your system comes up, wait until you see the "Optimizing System" box appear, continue to wait until the process is complete.
Now your Boot time is optimized and Prefetching should be properly enabled.
7. Time Windows boot with complete accuracy using Bootvis. Run another Trace and reboot. Now when Windows finishes loading the Bootvis tool you will see a time at the top of the Window that represent your optimized Boot time. Write this down.
8. Delete the ntosboot-b00dfaad.pf file in the \Windows\Prefetch folder. (This is never recommended except for these tests)
9. Time Windows boot again using Bootvis. Run another Trace and reboot. Now when Windows finishes loading the Bootvis tool you will see a time at the top of the Window that represent your unoptimized Boot time. Write this down.
10. Compare the times.
CMN - You HAVE NO IDEA WHAT YOU ARE TALKING ABOUT. Even on slow systems you boot times are improved with Prefetching, irrelevant to how many apps you have loading at startup. The exact amount of time that is changed varies based on MANY FACTORS but it is without a doubt SLOWER when you clean the folder = FACT. I work for a system OEM, have tested this on hundreds of machines of all varying speeds and have consulted fully on this issue with the Microsoft Client Performance Team. You Personally do not know how to properly test this even remotely. Go read up on this before you misinform more people, There is NO REASON TO CLEAN THE PREFETCH FOLDER PERIOD:
Here is some reference material:
Kernel Enhancements for Windows XP
Windows XP: Kernel Improvements Create a More Robust, Powerful, and Scalable OS
Benchmarking on Windows XP
•
•
•
•
Boot Prefetching
Windows XP speeds up system boot by observing the code and data needed each time the system is booted and prefetching the necessary file contents early in the boot process. This prefetching is not done until the third boot of the system, when sufficient information is available to make the prefetching most effective. The files observed during system boot will be used in the disk layout process mentioned above.
Application-Launch Prefetching
Windows XP also uses prefetching when launching applications. The files and the contents of the files accessed by each new process are observed and recorded. No prefetching can be done for the first launch of an application, so first launches are often considerably slower than subsequent launches. About 85% to 90% of the improvement is realized after just one launch of an application, with the remaining speed improvement coming after the system has had an opportunity to adjust the disk layout with information specific to this application.
One more time: do not clean out your Prefetch folder!
Tip of the day: Don’t clean out the Prefetch folder
Debunking yet another bogus Windows tip
Beware of Bogus XP Advice
Misinformation and the The Prefetch Flag
Anyone claiming any performance improvement from adjusting, tweaking, optimizing, cleaning or changing anything in relation to the default prefetcher registry settings, folder or files has either never tested it or improperly tested it. You will not find any fully documented, reproduceable testing in relation to these "performance" claims anywhere on the Internet
Testing Boot Prefetching:
Setup Requirements - Before beginning with testing you must confirm the following:
- Windows XP/Vista must have been cleanly installed from a non-nlite, lawfully owned, original installation CD.
- Your computer hardware must be in proper working order and properly configured.
- Your computer must not be overclocked.
- Your computer must not be infected with any Malware, Spyware or Viruses.
- Your computer must have a Hard Disk Drive, not a Solid State (flash-based) Drive.
- Prefetching must be enabled and working properly (it is by default).
Failure to meet all of these requirements will result in inaccurate timing results.
The following on a default installation of Windows will be done by Windows automatically at system idle times and roughly every 3 days.
1. Make sure the following Services are set to Automatic:
-Task Scheduler (It is by default but many people and bad tweaking programs disable it)
-COM+ Event System
2. Make sure Prefetching is properly enabled (it is by default) run the Prefetcher Fix: http://mywebpages.comcast.net/Suppor...XP.html#Tweaks
3. Reboot and make sure in the \Windows\Prefetch folder the following files are present:
-NTOSBOOT-B00DFAAD.PF
-Layout.ini
4. Reboot Windows and wait one full minute at the desktop so Windows can write the NTOSBOOT-B00DFAAD.PF file. Reboot Windows a second time and wait again 1 full minute. DO NOT install or change anything that would load during Windows Startup during any of this.
5. Download and install Bootvis. (Without using Bootvis you would have to wait 3 or more days for this optimization to happen automatically.) http://www.soft32.com/download_19687.html
6. In the menu go to "Trace" and select "Optimize System" and Reboot. This time when your system comes up, wait until you see the "Optimizing System" box appear, continue to wait until the process is complete.
Now your Boot time is optimized and Prefetching should be properly enabled.
7. Time Windows boot with complete accuracy using Bootvis. Run another Trace and reboot. Now when Windows finishes loading the Bootvis tool you will see a time at the top of the Window that represent your optimized Boot time. Write this down.
8. Delete the ntosboot-b00dfaad.pf file in the \Windows\Prefetch folder. (This is never recommended except for these tests)
9. Time Windows boot again using Bootvis. Run another Trace and reboot. Now when Windows finishes loading the Bootvis tool you will see a time at the top of the Window that represent your unoptimized Boot time. Write this down.
10. Compare the times.
•
•
Join Date: Feb 2007
Posts: 6
Reputation:
Rep Power: 0
Solved Threads: 0
Listen, I'm not saying that someone should clean their prefetch daily or anything like that, I am saying that My results with the prefetch have been that clearing out the prefetch has not increased MY boot times. In the event that someone does clean out their prefetch and it increases their boot times, it is no big deal, because within 3 reboots they will be back to normal, In the event of someone having a slower boot obviously it would NOT be advisable to keep cleaning the prefetch.
I have done boot speed testing with bootvis before, but I run linux now, and I am not going to dig up my old hd with xp on it for the sake of an argument. So, for this conversation, I am ending saying that I am Not recommending that everyone clear their prefetch, especially on a regular basis. I am saying that doing so did not effect my boot times, and if it effected yours, a few boots later it will be back to normal.
I am not going to post on this topic again, as it is not really that important..
I have done boot speed testing with bootvis before, but I run linux now, and I am not going to dig up my old hd with xp on it for the sake of an argument. So, for this conversation, I am ending saying that I am Not recommending that everyone clear their prefetch, especially on a regular basis. I am saying that doing so did not effect my boot times, and if it effected yours, a few boots later it will be back to normal.
I am not going to post on this topic again, as it is not really that important..
•
•
Join Date: Jan 2005
Posts: 24
Reputation:
Rep Power: 4
Solved Threads: 0
•
•
•
•
Listen, I'm not saying that someone should clean their prefetch daily or anything like that, I am saying that My results with the prefetch have been that clearing out the prefetch has not increased MY boot times. In the event that someone does clean out their prefetch and it increases their boot times, it is no big deal, because within 3 reboots they will be back to normal, In the event of someone having a slower boot obviously it would NOT be advisable to keep cleaning the prefetch.
I have done boot speed testing with bootvis before, but I run linux now, and I am not going to dig up my old hd with xp on it for the sake of an argument. So, for this conversation, I am ending saying that I am Not recommending that everyone clear their prefetch, especially on a regular basis. I am saying that doing so did not effect my boot times, and if it effected yours, a few boots later it will be back to normal.
I am not going to post on this topic again, as it is not really that important..
![]() |
•
•
•
•
•
•
•
•
DaniWeb Windows tips 'n' tweaks Marketplace
•
•
•
•
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
•
•
•
•
apple browser cd choose command computer console crack dell development download drm explorer fiji france ie 7 install internet leopard license linux media microsoft mobile news office online open operating operating system os phishing photo prompt registry root security server software source system ubuntu unix upgrade vista volume windows windows update windows vista xp
- Previous Thread: Cruel Trick
- Next Thread: Creating 'App paths'...



wow. I guess you're right.
Linear Mode