From: "Jim" <
[email protected]>
| I meant that running a process that periodically defrags is hardly ever
| useful.
|
| I really haven't been a fan of defragmenting routinely since my days as a
| VMS system manager. I can always cite examples where defragmenting makes a
| lot of difference as well as examples where it makes no difference at all.
| So, I defragment every now and then, but only when defrag tells me to.
| Usually, I see some change after defragging the data disk, but I can't
| really see any change after defragging the system disk.
|
| However, I doubt that there is anything on the OP's list that contributes to
| his problem (which my systems do not show).
|
| Jim
|
Fragmentation can be high and can dramatically slow down the computer. This can happen with
something like Outlook Express. It databases all the messages in folders and the process of
using it makes framented data storage. Internet Explorer can also. When IE takes a
percentage of the hard disk space like 1GB or more the IE cache gets data storage gets
fragmented.
When I say periodically I don't mean a weekly but a monthly or so defragmentation. When the
Windows hole folder get fragmentaed the OS is slowed down and bots take a little longer.
In Windows memory gets fragmented as well. If you leave a system on 24x7 and it does many
routines in the background, the memory gets fragmented over time and you can allieviate that
by an occasional reboot.
In context to this thread, a defragmentation of the hard disk is not warranted and will have
no affect on the CPU, SVCHOST.EXE or EXPLORER.EXE utilization.
I had a Dell Latitude D610 and many Dell Latitude D620s.
I had a Ghost Image of the D620 but not of the earlier model. I tried to restore the D620
image on the D610. They were close in hardware and chipsets. However they were different
enough to cause SVCHOST.EXE to have at 97 ~ 99% utilization and the system was an unusable
Dog. I eventually installed WinXP SP2 and the office suite if software on it from scratch
and the PC worked extremely well. There was no malware in the equation but a piece of
hardware associated with some driver that was causing a particular module of the OS to work
much harder and spike its utilization to where the PC overall was slow, sluggish and
unusable.