Is it possible to defragment registry?

[Guest]

Hello experts,

Is it possible to defragment registry the way files on a disk are
defragmented? Or, am I totally wrong?

If possible, then how?

Your help is greatly appreciated

 

[Guest]

yeh,

go to microsoft.com and
download a program by
sysinternals called pagedefrag.

then set it to run a boot time.

have fun!

--

<)))º>·´¯`·.¸. , . .·´¯`·.. ><)))º>`·.¸¸.·´¯`·.¸.·´¯`·...¸><)))º>

..

 

[R. McCarty]

It's not really defragmentation as much as removal of "White Space".
The operation generally compacts the registry resulting in a smaller
size. NTRegOpt is one program that does this.
http://www.larshederer.homepage.t-online.de/erunt/
Unless you've uninstalled lots of applications a normal NTRegOpt is
only going to provide a 4-7% size reduction.

Note: As with anything that changes the Registry, it's best to have a
current/verified image of your machine before using.

 

[JS]

Page Defrag
http://www.microsoft.com/technet/sysinternals/Utilities/PageDefrag.mspx

JS

 

[HeyBub]

Hello experts,

Is it possible to defragment registry the way files on a disk are
defragmented? Or, am I totally wrong?

If possible, then how?

Your help is greatly appreciated

Why do you ask? The registry is not accessed sequentially so it really
doesn't matter.

 

[VanguardLH]

in message

Is it possible to defragment registry the way files on a disk are
defragmented? Or, am I totally wrong?

The files for the registry are loaded into memory. It is the memory
copy that gets accessed. Memory is random access media. Doesn't
matter where in memory the data is contained. Getting to one byte in
memory is just as fast as getting to another byte. Also, when the
registry is loaded from the files into memory, there is no
fragmentation in the memory copy because it is a database.

Defragmentation will not removed orphaned entries in the registry.
Defragmentation will not reduce the Windows boot time until you have
something close to 33MB of orphaned entries to account for maybe all
of 1 second during the Windows boot to read the files to load the
registry into memory. Most registry defragmenting results in just a
dozen kilobytes or couple megabytes of whitespace that gets removed.
There will be no performance difference to *load* the registry files
(and absolutely none for the memory copy) for such a tiny change in
size of the .dat files.

Do you feel compelled to perform a possible hazardous operation on
your registry for such tiny gains?

 

[Tony Meloche]

It's not really defragmentation as much as removal of "White Space".
The operation generally compacts the registry resulting in a smaller
size. NTRegOpt is one program that does this.
http://www.larshederer.homepage.t-online.de/erunt/

A good description - NTRegOpt does indeed compress the registry some to
eliminate "white space", and is a solid, stable program (Ive used it for
years). Lars's other program, "ERU", is also excellent for making a back
up of the registry. But I'm speaking for myself here - I am the kind of
person who likes to have "backups for my backups".

Unless you've uninstalled lots of applications a normal NTRegOpt is
only going to provide a 4-7% size reduction.

If that - typically 2-3% if you use it about every thirty days.

Note: As with anything that changes the Registry, it's best to have a
current/verified image of your machine before using.

Absolutely. And as other posters will mention, while this is a good
safe tool for compressing the registry, that is hardly what you'd call a
critical maintenance step - I'm a user of the program, and I myself know
it's not really essential. I like things to be as tidy as possible on
my computer, that's all - different strokes.

BTW, the program is free.

Tony