More to the point, I don't think there is currently a simple way to prevent a non-plan class app from going to a machine that also can get an app for a specific plan class. If you wanted to to that you would need to make a plan class that excludes machines that fit the other plan classes. But the cpu_features list doesn't currently have a way of specifying a CPU without a given feature.
We could add negative features to the CPU features, i.e. "-avx" would mean "without avx", for example. On Wed, Aug 14, 2013 at 10:18 AM, Eric J Korpela <[email protected]>wrote: > Any processor with avx will also have pni, so you should expect both apps > to go to machines with AVX until the server can figure out which one is > faster on a given host (which is usually about 10 results if there's a > significant speed difference). If there is no speed difference, then both > with be sent for a long time. > > > > On Wed, Aug 14, 2013 at 9:57 AM, Radim Vančo <[email protected]> wrote: > >> I have set up a plan_class.xml but there is a problem with sending >> application. When I create new work, sometimes client download the specific >> procesor application but sometimes it download the normal version. It does >> usually after setting a new version the specific app and then after work >> creation it download normal version instead of specific. I have to cancel >> it via server management and create new one and the it download the >> specific app. If I cancel it in BOINC manager, it just download it again >> with the normal version of the app. Is there any option, something like >> <prefer_primary_platform> but for plan_class? It seems that it is randomly >> what application it download. >> Here is my plan_class, if it is allright: >> >> <plan_classes> >> <plan_class> >> <name>sse3<name> >> <cpu_feature>pni</cpu_feature> >> <projected_flops_scale>1.1</**projected_flops_scale> >> </plan_class> >> <plan_class> >> <name>avx<name> >> <cpu_feature>avx</cpu_feature> >> <projected_flops_scale>1.2</**projected_flops_scale> >> </plan_class> >> </plan_classes> >> >> ______________________________**_________________ >> boinc_dev mailing list >> [email protected] >> http://lists.ssl.berkeley.edu/**mailman/listinfo/boinc_dev<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.
