Skybuck Flying said:
2. Disable "dll cache" (command line command needed). [chop]
2. Very bad for performance. The dll cache is a folder on the
harddisk... How stupid ! At least my dutch dictionary says: "a cache
is a fast storage place etc". Harddisk are not fast at all lol..
especially not for many i/o operations. Anyway it seems windows
back's up commonly used dll's, compressess them, encrypts them,
decompressess them, decrypts them, and compares them, and loading and
storing ofcourse... All in all very much wastefull overhead. My dll
cache was once 500 MB !!! After disabling it (setting it to 1 MB) the
performance of my system skyrocketed... like no longer long stupid
harddisks spins/waits... the DLL cache probably got so full because I
compressed my drive and later decompressed it etc... windows got all
confused and didn't recognize the dll's and starting comparing them
to the dll cache or something... I dont know what the cause is or if
it's normal or not... the only thing I know is that the DLL cache is
a performance killer !
That might indeed be the only thing you know. One of the things you
*don't* know is what the DLLCache is actually used for. Windows does
*not* use the DLLCache during 'normal' operations, but only when
installing something, uninstalling something, or when running SFC
(System File Checker).
Since you're Dutch, I can understand that you don't know the original
meaning of the word "cache", which has nothing to do with speeding
things up, but is a place of storage. And that's exactly what DLLCache
is.
If a program you install overwrites a system DLL with an older and
incompatible version, the correct file can be restored from this
storage.
The cache is compressed (if using NTFS) to reduce disk space. Also,
with modern PCs, the CPU is so much faster than the hard drives anyhow
that it's *faster* to uncompress highly compressible files than to read
them uncompressed.
It's *highly* recommended that if you have installed multiple products,
you then open a command prompt and enter "sfc /SCANNOW" (you need your
installation media handy).
3. Auto backup/restore points are totaly ****ing useless and waste
harddisk space and processing power etc... A better solution is to
use a special backup utility like norton ghost etc... for full system
backup and easy restore... and/or a simply backup your data with
winzip etc.
Ghost can't revert registry entries, for one thing. It makes
*snapshots*, and, most importantly, you have to take the system down to
do it. That's even less efficient. Instead of a minor slowdown every
now and then, you lose hours while manually performing a Ghost snapshot.
WinZip can't correctly handle files that are locked ("in use"),
including your registry. It wasn't designed to do that job, and doesn't
do it well. It also can't handle NTFS streams or advanced protections
(WinRAR can, though), so restore from a zip file, and the files might
have wrong ownership and permissions, which might screw you up Big Time.
Unless you have a good backup program, the backup/restore point can be
what saves you. Ghost and WinZip are *not* backup programs, though.
4. Last access time... everytime a file or folder is accessed it
needs to be updated requiring more harddisk i/o operations... this is
a small performance improvement but still
For some apps it can
help a lot =D For example when a app needs to build a folder tree...
etc.. it's much faster now
On the other hand, system utilities that speed up the system by looking
at the access time of applications won't work, which causes a
*slowdown*. One example is disk defragmenters which place files
accessed recently near the start of the disk and files not accessed for
a long time near the end. Since the start of the disk usually is about
twice as fast as the end, and sometimes more, this makes sense.
Ofcourse I am always willing to listen to people who know other major
or small performance tweaks
Dont bother about posting the
graphical wizard to turn off special graphic effects... I know that
one already lol.. that's pretty easy thx to the wizard
but don't
hestitate if you know anything else
Sure: Don't post this to a.c.p.videocards.nvidia unless it contains
information directly relevant to nVidia video cards. Same goes for
a.c.p.mainboard.asus. You'll slow down our PCs when we have to download
your irrelevant (and largely incorrect) posts.
HTH, HAND,
