Changes between Version 99 and Version 100 of ProjectOptions

Timestamp:

Jun 2, 2010, 10:08:49 PM (15 years ago)

Author:

davea

Comment:

--

ProjectOptions

@@ -93 +93 @@
 Otherwise, the overall maximum is '''N*NCPUS + M*NGPUS)'''.
 
-{{{
+
+{{{
+<gpu_multiplier> GM </gpu_multiplier>
+}}}
+If your project uses GPUs, set this to roughly the ratio
+of GPU speed to CPU speed.
+Used in the calculation of job limits (see next 2 items).
+{{{
+<max_wus_to_send> N </max_wus_to_send>
+}}}
+Maximum jobs returned per scheduler RPC is '''N*(NCPUS + GM*NGPUS)'''.
+You can use this to limit the impact of faulty hosts.
+Default is 10.
+{{{
+<max_ncpus>N</max_ncpus>
+}}}
+An upper bound on NCPUS (default: 16)
+
+{{{
+<daily_result_quota> N </daily_result_quota>
+}}}
+Each host has a field MRD in the interval [1 .. daily_result_quota];
+it's initially daily_result_quota,
+and is adjusted as the host sends good or bad results.
+The maximum number of jobs sent to a given host in a 24-hour period is
+'''MRD*(NCPUS + GM*NGPUS)'''.
+You can use this to limit the impact of faulty hosts.
+
+== Job limits (advanced) ===
+The following is a
+more adaptable way of expressing limits on the number of jobs in progress on a host.
+You can specify limits for specific apps, and for your projects as a whole.
+Within each of these, you can specify limits for CPU jobs, GPU jobs, or total.
+In the case of CPU and GPU jobs, you can specify whether the limit should be
+scaled by the number of devices present on the host.
+
+This uses a separate config file, '''config_aux.xml'''.
+The syntax is:
+{{{
+<?xml version="1.0" ?>
+<config>
 <max_jobs_in_progress>
         <project>
@@ -114 +154 @@
         ...
 </max_jobs_in_progress>
-}}}
-A more adaptable way of expressing limits on the number of jobs in progress on a host.
-You can specify limits for specific apps, and for your projects as a whole.
-Within each of these, you can specify limits for CPU jobs, GPU jobs, or total.
-In the case of CPU and GPU jobs, you can specify whether the limit should be
-scaled by the number of devices present on the host.
-
-{{{
-<gpu_multiplier> GM </gpu_multiplier>
-}}}
-If your project uses GPUs, set this to roughly the ratio
-of GPU speed to CPU speed.
-Used in the calculation of job limits (see next 2 items).
-{{{
-<max_wus_to_send> N </max_wus_to_send>
-}}}
-Maximum jobs returned per scheduler RPC is '''N*(NCPUS + GM*NGPUS)'''.
-You can use this to limit the impact of faulty hosts.
-Default is 10.
-{{{
-<max_ncpus>N</max_ncpus>
-}}}
-An upper bound on NCPUS (default: 16)
-
-{{{
-<daily_result_quota> N </daily_result_quota>
-}}}
-Each host has a field MRD in the interval [1 .. daily_result_quota];
-it's initially daily_result_quota,
-and is adjusted as the host sends good or bad results.
-The maximum number of jobs sent to a given host in a 24-hour period is
-'''MRD*(NCPUS + GM*NGPUS)'''.
-You can use this to limit the impact of faulty hosts.
+</config>
+}}}
 
 === Job-cache scheduling ===