CPU time wrong
12 Aug 2005 20:22:46 UTC
Topic 189691
(moderation:
I've noticed that my E@H work units are finishing too late to get credit. After a little checking I've noticed that even when getting 100% CPU BOINC managed records about 10 seconds of CPU time on E@H for every 45 seconds that it's running.
Any ideas?
CPU time wrong
)
Hhmmm, that's strange --
I checked my crunchers very carefully, and although the time tag only updates about 6 second intervals, it keeps correct time, and correctly relates the time spent on the project. Check your application and utilization; perhaps you have two processes running at the same time (like S@H and E@H) and sharing the total resources. Just a thought ....
If I've lived this long - I gotta be that old!
RE: Any ideas? On your
)
On your Athlon XP 2200+, EAH results are taking just over 7 hours of CPU time which is perfectly normal for that CPU. If the result is consuming days of wall clock time then something else is consuming your CPU. Look in Task Manager and try to identify what it is.
Are you running other projects? If so, what are the resource shares? What "connect to network" setting are you using? It would seem to be far too large because you have a whole lot of work on hand which is going to expire.
Another thing to look at. Are you using the preference to stop work when the user is active? I've had a look at a couple of your results and they seem to stop and then resume far too many times. Maybe this is why nothing is getting done.
Edit: You should also consider upgrading from Boinc 4.25 to 4.45 as the later version is more likely to help you not miss deadlines.
Cheers,
Gary.
Task manager shows that E@H
)
Task manager shows that E@H is using 97-99% of the CPU, however the performance graph shows that between 20-80% of the cpu load is kernel time.
When any other BOINC app is running the kernel CPU load is down to around 2%.
OK, on further investigation
)
OK, on further investigation it's not just E@H, it's everything. Even when 100% cpu is going to the system idle process, the graph shows huge amouts of CPU being used by the kernel. My other PC is fine!
Thanks to a very helpful app
)
Thanks to a very helpful app by the name of 'process explorer' I've got to the bottom of this problem.
It was caused by a USB webcam, it was generating hardware interupts that were using around 60%-70% of the CPU. Why 'task manager' was showing that E@H was using 100% CPU, I don't know but 'process explorer' was able to correctly pinpoint where all the CPU was being used.
Glad you were able to get to
)
Glad you were able to get to the bottom of your problem. Sorry I wasn't much help, but I don't have a webcam running here, so I don't (didn't) see it ...
If I've lived this long - I gotta be that old!