Perhaps related: there has been a long standing problem with work requests on machines that have either 2 or more ATI/AMD GPUs or 2 or more NVIDIA GPUs. If both app_info.xml files and exclude statements are used WUs will not fetch work until the GPU queue runs completely dry and all WUs are reported. This is a big problem, especially with POEM as exclude statements are necessary due to the POEM apps high CPU usage.
A thread more completely documenting the problem: http://boinc.berkeley.edu/dev/forum_thread.php?id=7796#46223 The problem has been confirmed for both ATI/AMD and NVIDIA and the attempts at fixes in 7.0.36 and later in 7.0.38 have done nothing to resolve the issue. The only workaround at this point is to revert to BOINC 7.0.2 as all later builds exhibit this troublesome behavior. 7.0.2 has other problems, but less severe ones at least for those running apps such as POEM and with 2 or more similar GPUs. Regards/Ed (Beyond in the above listed thread) On Thu, Nov 8, 2012 at 1:44 AM, David Anderson <[email protected]>wrote: > I checked in these changes. > (Jeff, please deploy and test these on SETI@home beta at some point). > -- David > > On 07-Nov-2012 7:09 PM, David Anderson wrote: > > The current code resends lost jobs using the fastest app version, > > whether or not work is being requested for the devices it uses. > > There are 2 problems with this: > > > > - It can send work for devices that don't need it > > - It can send VLAR jobs to GPUs > > > > I'll check in changes to prevent these behaviors. > > May take me a day or two. > > > > -- David > > > > On 06-Nov-2012 4:37 PM, Stephen Maclagan wrote: > >> 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. > _______________________________________________ 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.
