| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Support
Forum: BOINC Agent Support
Thread: Run time very different from clock time? |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 9
|
|
| Author |
|
|
RicktheBrick
Senior Cruncher Joined: Sep 23, 2005 Post Count: 206 Status: Offline Project Badges: 
|
I have left my linux computer on for more than 30 hours straight and during that time I have sent back 2 results but when I look at the total run time it is only 13 hours. That includes the time on the present work unit. It seems to me that cpu time is less than a half of the time that the computer is actually on and processing the boinc program. My preferences are the default so there are no times when the program should be shut down. Most of the time no other programs are being executed too so why am I not getting the proper amount of run time and points?
|
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Hi RicktheBrick,
Run time is about the same as clock time, unless other factors intervene. The most obvious possibility is a result waiting for validation on the server. Less likely, but possible, is an invalid result that does not match the results sent back for that work unit by other members. Right now, until we finish implementing the BOINC system and have a results page showing the status of results (awaiting validation, valid, invalid) it is a bit hard to keep track of everything. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I saw it even worse: 2 hrs run time in about 24 hrs real time.
This all was caused by the screen saver. That was one the fancy ones who deal with large images - moving, rotating and so on. With a poor video card this needs a lot of CPU time. So I would recommend to choose a simple screensaver which blanks the screen only. hth Thomas Prause |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Good point, prause!
----------------------------------------I remember now that the screen saver had to be slowed down for the Human Proteome Folding project because it ate up too much time on low-end machines. Does anybody else see this happening on their computer? If so, what type of computer do you have? How about your computer, RicktheBrick? mycrofth Added: I have sent a note about this. [Edit 1 times, last edit by Former Member at Dec 1, 2005 10:38:07 AM] |
|||
|
||||
|
RicktheBrick
Senior Cruncher Joined: Sep 23, 2005 Post Count: 206 Status: Offline Project Badges:
|
I have a 1GHz celeron. I use Ubuntu linux. I have disabled the screensaver as I do not even have a monitor for the computer. I control the computer with vnc software and a different computer located in another location. I just watched boinc manager program and watched its cpu time and compared it to the computer's time. It took 1 minute and 50 seconds of the computer's time for the boinc manager's cpu time to increase by 1 minute. I am doing well as I have had 6 results in the last two days but have been given only 38 hours of credit compared to at least 48 hours of real time.
|
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
i run ubuntu too.
i have problems with total run time as well. I just sent a unit whose calculation time did not appear right in boinc to begin with. more precisely: unit started at 19:18. unit finished the following day at 8:51. boinc stated run time: 8:51. it seems boinc resets its timer at the beginning of each day or something. Anyway, its not right. I left my machine up and running boinc constantly and online since i installed boinc and i only have 11hours of recorded work time per day. Not right. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Just since nobody has mentioned it in this thread yet: as far as I know, the UD client uses wall clock time, but the BOINC client uses process time, i.e. the precise time that the WCG thread has spent being executed, and not counting the time when other processes have been using the CPU.
The different points systems then account for this by calculating points totally differently. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
 Hello,I think a result page that you get with most Boinc projects.I am glad this is comming to fruition.This time problem is with this Box also.LinuxOS 9.2 {live Disrtro c/d} uses KDE 3.5.1 which just came in from 3.5. Am running a Rosetta W/U for WCG,after 10 hours it is finally at 50%.Was advised at another thread to keep crunching it due to the possibility of BIG w/u out there. Thanks for the Result page.{any idea when this will come to fruition?} Sincerely Doug Worrall |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
i ran the last mentionned unit during the night, where it constantly enjoyed about 85-90% of my cpu.
the fact that the recorded time for the unit matched exactly the time of the new day, i find it hard to beleive it was just a coincidence --- then again, i will confirm or disconfirm that claim by watching closely what happens tomorrow. |
||
|
|
|