After 7.2.42 - what about not running unfinished jobs!?

Message boards : Number crunching : After 7.2.42 - what about not running unfinished jobs!?
Message board moderation

To post messages, you must log in.

AuthorMessage
DanHansen@Denmark
Volunteer tester
Avatar

Send message
Joined: 14 Nov 12
Posts: 194
Credit: 5,881,465
RAC: 0
Denmark
Message 1570170 - Posted: 10 Sep 2014, 22:54:07 UTC
Last modified: 10 Sep 2014, 22:54:44 UTC

Hi,


Since the 7.2.42 update jobs are reported when done, but what about those unfinished jobs? Sometimes the system starts chewing on a new job, before being done with some of the jobs. I don't know why!? If it's because of a reboot or some other system glitch. In the older versions, jobs were only reported, when all downloaded jobs were done! Does Boinc somehow fix this by itself or do you have to change "priority" of the jobs not done?
Project Headless CLI Linux Multiple GPU Boinc Servers
Ubuntu Server 14.04.1 64bit
Kernel 3.13.0-32-generic
CPU's i5-4690K
GPU's GT640/GTX750TI
Nvidia v.340.29
BOINC v.7.2.42

ID: 1570170 · Report as offensive
Profile BilBg
Volunteer tester
Avatar

Send message
Joined: 27 May 07
Posts: 3720
Credit: 9,385,827
RAC: 0
Bulgaria
Message 1570185 - Posted: 10 Sep 2014, 23:45:12 UTC - in response to Message 1570170.  

In the older versions, jobs were only reported, when all downloaded jobs were done!

Not true for any BOINC version
 


- ALF - "Find out what you don't do well ..... then don't do it!" :)
 
ID: 1570185 · Report as offensive
Profile HAL9000
Volunteer tester
Avatar

Send message
Joined: 11 Sep 99
Posts: 6534
Credit: 196,805,888
RAC: 57
United States
Message 1570206 - Posted: 11 Sep 2014, 0:36:14 UTC

It is normal behavior for BOINC to report work when it requests more work. Perhaps your system is just requesting work more often?
There is an option for the cc_config.xml to set report_results_immediately. If you want BOINC to specifically report every job once complete even when not requesting new work.
SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[
ID: 1570206 · Report as offensive
Josef W. Segur
Volunteer developer
Volunteer tester

Send message
Joined: 30 Oct 99
Posts: 4504
Credit: 1,414,761
RAC: 0
United States
Message 1570274 - Posted: 11 Sep 2014, 1:55:55 UTC

BOINC 7.2.42 does report tasks immediately when No New Tasks is set, IIRC a reaction to a complaint from a user who set NNT before going on a holiday break and came back to find that much of the work which had been uploaded before the setting change had not been reported so didn't get credit. A related change is that the report is done no later than one hour after task completion (that was formerly 24 hours).
                                                                   Joe
ID: 1570274 · Report as offensive
Claggy
Volunteer tester

Send message
Joined: 5 Jul 99
Posts: 4654
Credit: 47,537,079
RAC: 4
United Kingdom
Message 1570377 - Posted: 11 Sep 2014, 8:29:14 UTC - in response to Message 1570185.  

In the older versions, jobs were only reported, when all downloaded jobs were done!

Not true for any BOINC version

That could happen with Boinc 7.0.x if you set your cache settings incorrectly,

with a Cache setting of 0 + 0.5 Boinc would ask for half a day's work, then wait for all the work to be done before asking again,
somewhere in the Boinc development after that, as well as reporting tasks after an hour, Boinc 7.2.x will also piggy-back a request when reporting,
instead of waiting until the minimum value had been reached.

Claggy
ID: 1570377 · Report as offensive

Message boards : Number crunching : After 7.2.42 - what about not running unfinished jobs!?


 
©2024 University of California
 
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.