I agree that there is a bug here...  It's not the only bug in the best
app version logic in the scheduler.  At times and without explanation
the beta app version logic chooses a version which is not the best,
not due to the random choice logic, but for some unexplained reason.

On Wed, Nov 7, 2012 at 8:48 AM, Josef W. Segur <[email protected]> wrote:
> The resend lost work feature was added to BOINC long before it supported 
> multiple devices, and does no checking of what app_version the original 
> assignment used. For instance, a lost SETI WU with the .vlar extension which 
> was originally assigned to CPU is often expired immediately on the next 
> request because resend lost work is working on the basis that a GPU 
> app_version is "best". What Claggy has documented is instances where the best 
> app_version logic has wrongly chosen a version which uses a device for which 
> no work was requested.
> --
>                                                           Joe
>
>
> On Wed, 07 Nov 2012 10:29:30 -0500, McLeod, John <[email protected]> wrote:
>
>> A resend of a lost task is not the same as a fresh work assignment.  These 
>> tasks has already been assigned to that device by the server at some 
>> previous time, and succeeded in getting lost in transit.  They will not be 
>> reassigned to a different computing device on your computer.
>>
>> -----Original Message-----
>> From: [email protected] 
>> [mailto:[email protected]] On Behalf Of Stephen Maclagan
>> Sent: Tuesday, November 06, 2012 7:38 PM
>> To: [email protected]
>> Subject: [boinc_dev] Seti Beta scheduler resends work to a GPU that didn't 
>> ask for it.
>>
>> I get the impression that the present scheduler is broken in some
>> respect, on both my i7-2600K/GTX460/HD7770 and my E8500/GTX9800+ hosts
>> they will request work for one device, then get sent work for another
>> device that wasn't requesting work:
>>
>>
>> 01/11/2012 19:02:57 SETI@home Beta Test Reporting 2 completed tasks,
>> requesting new tasks for CPU and GPU
>>
>>  01/11/2012 19:02:57 SETI@home Beta Test [sched_op_debug] CPU work
>> request: 64.03 seconds; 0.00 CPUs
>>
>>  01/11/2012 19:02:57 SETI@home Beta Test [sched_op_debug] NVIDIA GPU
>> work request: 0.00 seconds; 0.00 GPUs
>>
>>  01/11/2012 19:02:57 SETI@home Beta Test [sched_op_debug] ATI GPU work
>> request: 3768.39 seconds; 1.00 GPUs
>>
>>  01/11/2012 19:05:32 SETI@home Beta Test Scheduler request completed:
>> got 4 new tasks
>>
>>  01/11/2012 19:05:32 SETI@home Beta Test [sched_op_debug] Server
>> version 701
>>
>>  01/11/2012 19:05:32 SETI@home Beta Test Message from server: Resent
>> lost task 05ap10al.26099.13160.8.14.143_1
>>
>>  01/11/2012 19:05:32 SETI@home Beta Test Message from server: Resent
>> lost task 05ap10al.12468.72.9.14.67_0
>>
>>  01/11/2012 19:05:32 SETI@home Beta Test Message from server: Resent
>> lost task 05ap10al.12468.72.9.14.68_0
>>
>>  01/11/2012 19:05:32 SETI@home Beta Test Message from server: Resent
>> lost task 05ap10al.12468.72.9.14.69_0
>>
>>  01/11/2012 19:05:32 SETI@home Beta Test Project requested delay of 7
>> seconds
>>
>>  01/11/2012 19:05:32 SETI@home Beta Test [sched_op_debug] estimated
>> total CPU job duration: 0 seconds
>>
>>  01/11/2012 19:05:32 SETI@home Beta Test [sched_op_debug] estimated
>> total NVIDIA GPU job duration: 3306 seconds
>>
>>  01/11/2012 19:05:32 SETI@home Beta Test [sched_op_debug] estimated
>> total ATI GPU job duration: 0 seconds
>>
>>  01/11/2012 19:05:32 SETI@home Beta Test [sched_op_debug]
>> handle_scheduler_reply(): got ack for result 05ap10al.
>> 26207.12342.140733193388040.14.220_1
>>
>>  01/11/2012 19:05:32 SETI@home Beta Test [sched_op_debug]
>> handle_scheduler_reply(): got ack for result 05ap10al.
>> 26207.12751.140733193388040.14.183_1
>>
>>  01/11/2012 19:05:32 SETI@home Beta Test [sched_op_debug] Deferring
>> communication for 7 sec
>>
>>  01/11/2012 19:05:32 SETI@home Beta Test [sched_op_debug] Reason:
>> requested by project
>>
>>
>>
>> I did initially report it on Seti Beta:
>>
>>
>> http://setiweb.ssl.berkeley.edu/beta/forum_thread.php?id=1950&postid=44291
>>
>>
>>
>> Turning off Use Nvidia GPU in the project preferences stops work being
>> resent to the Nvidia GPU when it wasn't asking for it,
>> i can then get CPU work resent to the ATI GPU when it wasn't
>> asking for it instead,
>>
>>
>>
>> Claggy
> _______________________________________________
> boinc_dev mailing list
> [email protected]
> http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
> To unsubscribe, visit the above URL and
> (near bottom of page) enter your email address.
_______________________________________________
boinc_dev mailing list
[email protected]
http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.

Reply via email to