HACK: To load Applications Faster.
For every application you run on windows there is component names Prefetcher in Microsoft windows. It is a component of the Memory Manager that speeds up the Windows boot process, and shortens the amount of time it takes to start up programs. The Windows prefetcher aims to load applications faster by “prefetching” the application and storing it in the pre-fetch cache. When a Windows system boots, a large number of files need to be read into memory and processed.
This includes:
- loading different segments of the same file at different times. As a result, a significant amount of time is spent opening and accessing files multiple times, where a single access would be more efficient. The prefetcher works by watching what code and data is accessed during the boot process (including reads of the NTFS Master File Table), and recording a trace file of this activity.
- Next time when system boots. This information recorded in this trace file can be used to load code and data in a more optimal fashion.
- The boot prefetcher will continue to watch for such activity until 30 seconds after the user's shell has started, or until 60 seconds after all services have finished initializing, or until 120 seconds after the system has booted, whichever elapses first.
You can speed up application loading by changing the default value of one the settings under the relevant key.
Navigate to:
HLM\SYSTEM\CurrentControlSet\Control\SessionManager\Memory Management\PrefetchParameters
Value can be set to following:
0 = Disabled, 1 = Application launch prefetching enabled, 2 = Boot prefetching enabled,
3 = Applaunch and Boot enabled (Optimal and Default).
The default value for the EnablePrefetcher setting is 3. You can go up to 9.
Reboot the system to take change effect.
HACK: For loading boot files fast.
Generally while file is fragmented it gets scattered over all over hard disk. This further affects the files that load at boot time. You can defragment the files that load at system startup to enable faster loading.
Navigate to:
HLM\SOFTWARE\Microsoft\Dfrg\BootOptimizeFunction
set to Y (forYes) for setting called Enable under this key. This setting defragments the boot files, and it relocate startup files into contiguous clusters on the volume, reducing the movement of the disk head when reading the volume. With the setting at Y, boot file optimisation occurs automatically if the system is idle for 10 minutes.
Reboot the system to take the change effect.
HACK: To make application load on priority.
In operating system multiple instances of the same application shares a single process thread. If you have stability problems or slow application loads, launching each application in its own process will improve stability and speed up load times.
Navigate to:
HLM\SYSTEM\CurrentControlSet\Control\PriorityControl
Optimise XP’s process priority control by setting the DWORD Value for Win32PrioritySeperation to… well, the default is 2, and 27, 28, 37, 38, and more have all been quoted as good values (in decimal). However, note that that each process will consume the same amount of memory: this hack is therefore only recommended if you have 512 MB or more of system RAM.
No reboot is required.
HACK: to unload Unused Dynamic Link Library
Dynamic-link library as you all must be knowing is Microsoft's implementation of the shared library concept in the Microsoft Windows and OS/2 operating systems. These libraries usually have the file extension DLL, OCX (for libraries containing ActiveX controls), or DRV (for legacy system drivers). The file formats for DLLs are the same as for Windows EXE files — that is, Portable Executable (PE) for 32-bit and 64-bit Windows, and New Executable (NE) for 16-bit Windows. As with EXEs, DLLs can contain code, data, and resources, in any combination.
So every time an application is closed, XP has the annoying habit of leaving the associated DLL files in memory. This can hog precious resources and memory, and also cause stability problems. If you wish you can make these DLLs unload themselves from memory after the program is done running.
Navigate to:
HLM\SOFTWARE\Microsoft\Windows\CurrentVersion\ Explorer\AlwaysUnloadDLL
If the DWORD AlwaysUnloadDLL is not present, you will need to create it. Set the Value of the “(Default)” setting to 1. Application-associated DLLs will get unloaded when the application is closed.
No comments:
Post a Comment