CPU performace is >50% after installation of XP Pro

  • Thread starter Thread starter earlyadopter
  • Start date Start date
E

earlyadopter

After installing Windows XP professional and before
installing any programs I checked my Performance Monitor
for CPU activity. I found it to be excessively high, yet
no processes were running to explain this. I replaced the
CPU and that did not have any affect on the display. The
machine does not exhibit any symptoms of the condition,
but of course I am not running any programs either. What
could be going on here? Please help.
 
After installing Windows XP professional and before
installing any programs I checked my Performance Monitor
for CPU activity. I found it to be excessively high, yet
no processes were running to explain this. I replaced the
CPU and that did not have any affect on the display. The
machine does not exhibit any symptoms of the condition,
but of course I am not running any programs either. What
could be going on here? Please help.
Click to expand...

Try refreshing the Task Manager to be sure the CPU usage is a current
reading. If still high, check to see if the Indexing Service is running. On a
new installation of XP, the files are still being indexed (to improve search
capabilities). This service seems to be more useful for network situations.
Most home users find that that the indexing is not very beneficial and
disable it. You can disable it in Services and/or in the properties sheets
for each drive: uncheck the box next to "Allow Indexing on this drive..."

Also, a new installation of XP is quite busy optimizing itself based on the
usage patterns. You can speed this process up by running Disk
Defragmenter several times during the first week or two.
 
Also, a new installation of XP is quite busy optimizing itself based on the
usage patterns. You can speed this process up by running Disk
Defragmenter several times during the first week or two.
Click to expand...

I am intrigued by this statement. If you don't mind my asking, can
you explain why it is useful to defragment more than once in the first
week or two?

Please Let Me Know.
 
| On Mon, 3 Nov 2003 14:32:37 -0600 Sharon F <[email protected]>
| wrote the following and gave me the chance to write something equally
| inane:
|
| >Also, a new installation of XP is quite busy optimizing itself based
on the
| >usage patterns. You can speed this process up by running Disk
| >Defragmenter several times during the first week or two.
|
| I am intrigued by this statement. If you don't mind my asking, can
| you explain why it is useful to defragment more than once in the first
| week or two?
|
| Please Let Me Know.

........RTFM.......
 
I am intrigued by this statement. If you don't mind my asking, can
you explain why it is useful to defragment more than once in the first
week or two?

Please Let Me Know.
Click to expand...

Disk Defragmenter optimizes file placement based on data collected to the
Prefetch folder. This happens when you manually run the program and when
XP's own self optimizing tasks that run during idle moments. The self
optimizing is a "light" run of defrag - not as thorough as a manual run.

On most new setups, there is not a lot of idle time. New software is being
installed, patches applied, and so on. Consequently, when the self
optimizing occurs on a new setup there are many more files that need
placement. The short spurts of optimization are seen as disk activity and
in some cases as a hit on performance.

By taking a few extra minutes to run defrag, you can get that optimizing
done and out of the way instead of waiting for the idle time optimization
to do it in spurts. Running it a few times during those first few weeks also
keeps up with the newly devoloping usage patterns.
 
Disk Defragmenter optimizes file placement based on data collected to the
Prefetch folder. This happens when you manually run the program and when
XP's own self optimizing tasks that run during idle moments. The self
optimizing is a "light" run of defrag - not as thorough as a manual run.

On most new setups, there is not a lot of idle time. New software is being
installed, patches applied, and so on. Consequently, when the self
optimizing occurs on a new setup there are many more files that need
placement. The short spurts of optimization are seen as disk activity and
in some cases as a hit on performance.

By taking a few extra minutes to run defrag, you can get that optimizing
done and out of the way instead of waiting for the idle time optimization
to do it in spurts. Running it a few times during those first few weeks also
keeps up with the newly devoloping usage patterns.
Click to expand...

Its always a pleasant surprise to read such an intelligent,
considerate, and informative reply. Thank you for it.
 
Back
Top