================================================== ===
INTRODUCTION: (this is for folks that have more than 1 harddisk)
================================================== ===
Many folks today, who possess more than 1 harddisk, realize the benefits gained by moving their pagefile.sys (paging file) off of their main C: drive (where their Operating System AND Program Files usually are by default), so that the main disk is NOT "burdened" by the excessive head movements, & other forms of I/O (such as disk & memory) used on said main disk C:, for paging operations... The movement of logging files such as the EventLogs (& others also from applications + other OS logs) to another HDD is MUCH LIKE the reason exists for moving web browser caches to another disk as well!
(Which is often controlled via a web browser programs' GUI interface for configuration via its menus for this, OR, its .ini configuration files &/or registry entries).
The same idea can extend to logging from other apps as well, not just web browsers! Logs from apps, such as WinZip which does this via its configuration screens in its menus from its GUI interface, which many applications offer you the option of relocating their logs (from within their menu of options for configuring them) & even DrWtsn32.exe (the crash dump log controller in the Operating System) for example.
You can do more even such as altering the default user %tmp/temp% variables, so that temp "scratch file operations" also take place elsewhere, because they are happening nearly ALL the time too.
CONTROL PANEL-> System Icon/Advanced Tab/Environment button (temp & tmp variables (BY USER, & also SYSTEMWIDE)) as well as logs noted here + pagefile.sys (System Icon, Performance tab, Advanced button section)) In this case, however, this post?
It's SPECIFICALLY for the OS' EventLogs (not webbrowser caches, %tmp/temp% environment variable value location of "scratch/temp" files, or paging files in pagefile.sys - though, these too, follow the SAME idea/principal & lend you performance AND efficiency gains as well).
================================================== ===
HOW TO MOVE EVENT LOGS TO ANOTHER HDD (simple to do):
================================================== ===
Go here in the registry, using regedit.exe ->
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\Eventlog\Security
&
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\Eventlog\System
&
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\Eventlog\Application
First.
These are the "default logs" that every Windows NT-based OS has (2000/XP/Server 2003, & VISTA iirc also + quite possibly even as far back as NT 3.x - 4.0 also).
Then, the value entries beneath those keys in VALUES concerned here to edit in each of those (possibly others like IE7 has, or apps like SQLServer & even 3rd party apps, etc. et al), is the FILE value beneath each one.
Those FILE entries values for each key path noted above are where you move those files from their original default values, to another diskdrive & folder for recording their data for read/write I-O...
================================================== ===
LOGIC/REASONING & GAINS POSSIBLE (& how/what/where/why):
================================================== ===
This is done, to:
A.) Decrease the head movement of your diskdrive heads for logging
... vs. say for example, reading/writing to files on your main C: disk? Let another lesser used HDD do that!
-----------------------------------------------------------------------
B.) For picking up programs & even data faster!
(because your MAIN C: disk head movement is lessened) ...
-----------------------------------------------------------------------
C.) Movement of log files to another HDD is also done to lessen fragmentation of the log files (and others like webpage caches &/or temp ops) & other files also!
(fragmentation of the logs themselves, but also of other files being created &/or extended too).
-----------------------------------------------------------------------
D.) Additiionally, as a last benefit?
You can either archive, OR delete, the original logs & get space back too, as a bonus, on your main C: disk as well (as well as potentially helping to EXTEND ITS LIFE AS WELL, bu not having logs on the main C: disk, which is doubtless your most active constantly? It works less than it would WITH THE LOG FILES ON IT!!).
-----------------------------------------------------------------------
IMPORTANT:
-----------------------------------------------------------------------
I strongly recommend using another diskdrive, not a partition of your C: drive, & IF POSSIBLE!
(... AND, one placed onto another "I/O circuit" (diskdrive IDE/SATA/SCSI variants slots &/or cables), for maximum possible gain, using another set of read-write heads from another mechanical HDD instead of the ones on your programs & OS housing main C: disk (usually it is C
for BEST in gains doing this technique here).
PLUS, doing so, helps... simply also by lessening fragmentation of said files (logs, note what I stated above about placing them onto a disk with a good %-age of freespace left on them as well, IF possible) hopefully & that of other files being created &/or extended also as they are created OR, added to.
************************************************** *******************
So, even though today's NCQ & TCQ utilizing diskdrives employ "smart elevator" type algorithms to order disk I/O intelligently? ONCE MORE - Removing that burden (of logging, webbrowser cache population & reads, %temp% operations, etc. from this guide) IS ONE OF THE BEST THINGS YOU CAN DO to help make your default usual MAIN C: disks perform that much faster + efficiently (actually possibly saving power too)!
APK