As described in #4490, CMS needs a wide-area glidein pool with 200,000 cores. We have a test setup that simulates a large pool to see how we can scale to that level. We use only a fraction of the normal hardware for execute nodes by running many startds per core and running sleeps jobs that don't consume CPU or memory.
+{subsection: StartD}
+{verbatim}
+UPDATE_INTERVAL=$RANDOM_INTEGER(540, 740, 1)
+{endverbatim}
{subsection: Central Manager}
The central manager is cmssrv242.fnal.gov. It has 64GB of memory and 16 cores. It has a collector tree with 200 child collectors.
@@ -100,8 +104,9 @@
MAX_FILE_DESCRIPTORS=10512
NEGOTIATOR_MAX_TIME_PER_SUBMITTER=600
NEGOTIATOR_MAX_TIME_PER_PIESPIN=500
-NEGOTIATOR_MAX_TIME_PER_CYCLE=890
+NEGOTIATOR_MAX_TIME_PER_CYCLE=1500
NEGOTIATOR_TRIM_SHUTDOWN_THRESHOLD=300
+NEGOTIATOR_MAX_TIME_PER_CYCLE=1500
{endverbatim}
{subsection:Submit Machines}