What is the CPU doing?
7 Jul 2005 18:54:19 UTC
Topic 189501
(moderation:
Hello,
This is my computer:
CPU type GenuineIntel Intel(R) Pentium(R) 4 CPU 2.40GHz
Number of CPUs 1
Operating System Microsoft Windows XP Professional Edition, Service Pack 2, (05.01.2600.00)
I switch it on at 0600, and then I go to work.
When I get back, 11 hours later, it tells me that it has computed for about 1 hour of CPU time.
i.e., if I left it showing 38 minutes of CPU time, and 9 hours to completion, when I get back I find it showing 1:40 of CPU time, and 8:08 to completion.
Therefore, it is always seems to be running late, with the report deadline looming ahead.
The Task Manager shows E@H using 90%+ of the CPU time, so why does it seem that while I am away it does not work?
In the power management suspend is disabled, standby is disabled, the only thing switching off is the monitor.
Is it possible that when the monitor switches itself off E@H stops working?
What is the CPU doing?
)
Doubt it... How many projects are you involved in?
Maybe a serios overheating
)
Maybe a serios overheating problem
Be sure that your fan is free of dust.
As I attached in January my first WU took 11 hour on my AMD XP-M 2600+
In April a WU took about 14 hours, so I decided to open my laptop. I cleared the fan from dust and after that little operation a WU was done in 6,5 - 7 hours.
Till last week my hard disk died.
RE: Doubt it... How many
)
E@H.
RE: Maybe a serios
)
AsusProbe says that the CPU is at 52C/127F, and the PC has been switched on since 0600, i.e. almost 18 hours..
What about spyware and
)
What about spyware and trojans?
Maybe there is one active.
RE: What about spyware and
)
SpyBot and AVG have always been active and updated, ever since the the last time I re-installed the OS from scratch.
They show nothing, and also the Task Managers shows no suspect looking processes running.
Looks almost like you have
)
Looks almost like you have ended the first wu and began on the second...
But the 7 day return delay doesn't fit in here. ;)
You could install Process Explorer and make a similar run and then see in this program how
much cputime every process has taken and hopefully nail the cpuhog. ;)
RE: Looks almost like you
)
Will try that next week...
In the meantime:
6084163 1454576 3 Jul 2005 7:38:34 UTC 10 Jul 2005 11:45:33 UTC Over Success Done 35,315.08 77.36 0.00
Granted credit zero.
One of the problems is that BOINC requests seconds of work too soon, so they sit in the cache for days, without need...
RE: One of the problems is
)
What is your 'connect to' setting? The scheduler is smarter than it used to be, but you should still use a sensible cache size.
RE: RE: One of the
)
Never modified it...
Connect to network about every 0.1 days