In sched_reply.xml I see the the scheduler assigned number of threads wrong:
<platform>windows_x86_64</platform>
<plan_class>16t</plan_class>
<avg_ncpus>1.000000</avg_ncpus>
<max_ncpus>1.000000</max_ncpus>
<flops>3718491507.830066</flops>
<cmdline> --nthreads 1</cmdline>
yoyo schrieb:
> Hello,
>
> in https://yafu.myfirewall.org/yafu I have a yafu-16t app which requires
> at least 16 cores. But Boinc runs it only with one thread?
>
> I have also a -8t and -4t app. But the problematic one is the -16t.
> The plan_class_spec for 16t and 8t:
> <plan_class>
> <name> 16t </name>
> <min_ncpus> 16 </min_ncpus>
> <nthreads_cmdline/>
> </plan_class>
> <plan_class>
> <name> 8t </name>
> <min_ncpus> 8 </min_ncpus>
> <max_threads> 8 </max_threads>
> <nthreads_cmdline/>
> </plan_class>
>
> You get the 16t app if you have at least 16 cores. This works fine on
> the scheduler. To simulate 16 cores I used cc_config.xml with
> <ncpus>16</ncpus>. Those are recognized in boinc message log.
>
> The app is a wrapper app. The wrapper was not modified and is the same
> as for th 8t, 4t app.
>
> The attached log is from Boinc version 7.6.22, but it happens also with
> 7.6.33. In the log a 8t with 8 threads is started:
>
> 22.04.2017 10:42:50 | yafu | [cpu_sched_debug] 0:
> yafu_ali_350688_L136_C132_1490458205_177_0 (MD: yes; UTS: no)
>
> And a 16t, but only with 1 thread:
>
> 22.04.2017 10:42:50 | yafu | [cpu_sched_debug] 1:
> yafu_ali_116040_L141_C136_1472325323_8_3 (MD: no; UTS: no)
>
> Why and what does 'MD: no' means?
>
> yoyo
>
>
> ---
> Diese E-Mail wurde von AVG auf Viren geprüft.
> http://www.avg.com
>
>
>
> _______________________________________________
> boinc_projects mailing list
> [email protected]
> https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_projects
> To unsubscribe, visit the above URL and
> (near bottom of page) enter your email address.
>
_______________________________________________
boinc_dev mailing list
[email protected]
https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.