Index  | Recent Threads  | Unanswered Threads  | Who's Active  | Guidelines  | Search
 

Quick Go »
No member browsing this thread
Thread Status: Active
Total posts in this thread: 4
[ Jump to Last Post ]
Post new Thread
Author
Previous Thread This topic has been viewed 1012 times and has 3 replies Next Thread
kateiacy
Veteran Cruncher
USA
Joined: Jan 23, 2010
Post Count: 1027
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
elapsed time is not wallclock time when CPU usage is set less than 100%

I am running BOINC 6.10.17 under Ubuntu 10.04 on several machines. I have observed that the "elapsed time" shown in the BOINC manager matches the true wallclock time on the two machines for which I have set CPU usage to 100%.

However, on the laptops on which CPU usage is set to 65%, the "elapsed time" shown is only 65% of the actual wallclock time.

So elapsed time seems to actually mean amount of CPU time requested. Is that intended?
----------------------------------------

[Sep 22, 2010 12:26:27 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Sekerob
Ace Cruncher
Joined: Jul 24, 2005
Post Count: 20043
Status: Offline
Reply to this Post  Reply with Quote 
Re: elapsed time is not wallclock time when CPU usage is set less than 100%

Yes, or differently, elapsed is the time that BOINC is not suspended and a task is switched on to use any spare CPU cycles, which is again less than that On/Elapsed time depending on how efficient a device is and other momentary loads.

The reason that the developers adopted the Elapsed was that the GPU cards/sciences as of yet have no concept of timekeeping, so the wallclock time is used to compute the contribution. GPU jobs either run all out or not at all, so to them Elapsed time is equal GPU time.

edit: spelling.
----------------------------------------
WCG Global & Research > Make Proposal Help: Start Here!
Please help to make the Forums an enjoyable experience for All!
----------------------------------------
[Edit 1 times, last edit by Sekerob at Sep 22, 2010 12:44:24 PM]
[Sep 22, 2010 12:39:52 PM]   Link   Report threatening or abusive post: please login first  Go to top 
kateiacy
Veteran Cruncher
USA
Joined: Jan 23, 2010
Post Count: 1027
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: elapsed time is not wallclock time when CPU usage is set less than 100%

Thanks for the explanation.

I run a couple of GPU BOINC projects on my machines while the CPUs run WCG. For GPU projects, does the CPU time shown in BOINC manager mean the time when the CPU was assisting, and elapsed time means the GPU time? The CPU time shown for GPU projects is much smaller than elapsed, so that would make sense.
----------------------------------------

[Sep 22, 2010 6:43:51 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Sekerob
Ace Cruncher
Joined: Jul 24, 2005
Post Count: 20043
Status: Offline
Reply to this Post  Reply with Quote 
Re: elapsed time is not wallclock time when CPU usage is set less than 100%

Correct, no matter what GPU job, some cpu time is needed to interface between the different parts of the system. Some GPU projects use very little, a few percent, some use a bit more. Most of the cases a CPU core handles 2 tasks when e.g. WCG and Collatz is run. On a regular quad with 2 GPU cards you could thus have 6 tasks running. There are also GPU projects where the full CPU core is reserved + the GPU, so only 4 tasks would run on a quad... that is, what I've been reading around. I could be wrong.
----------------------------------------
WCG Global & Research > Make Proposal Help: Start Here!
Please help to make the Forums an enjoyable experience for All!
[Sep 22, 2010 6:59:07 PM]   Link   Report threatening or abusive post: please login first  Go to top 
[ Jump to Last Post ]
Post new Thread