[Swift-commit] r5273 - branches/release-0.93/docs/siteguide

[ketan at ci.uchicago.edu]

Author: ketan
Date: 2011-11-07 13:46:44 -0600 (Mon, 07 Nov 2011)
New Revision: 5273

Modified:
   branches/release-0.93/docs/siteguide/beagle
Log:
corrected sites terminology and meanings

Modified: branches/release-0.93/docs/siteguide/beagle
===================================================================
--- branches/release-0.93/docs/siteguide/beagle	2011-11-02 05:41:17 UTC (rev 5272)
+++ branches/release-0.93/docs/siteguide/beagle	2011-11-07 19:46:44 UTC (rev 5273)
@@ -53,8 +53,8 @@
 The following sites.xml parameters must be set to scale that is intended for a large run:
 
  * *maxTime* : The expected walltime for completion of your run. This parameter is accepted in seconds.
- * *slots* : Number of qsub jobs needs to be submitted by swift. This number will determine how many qsubs swift will submit for your run. Typical values range between 40 and 80 for large runs.
- * *nodeGranularity* : Determines the number of nodes per job. Total nodes will thus be slots times nodegranularity. This may vary for advanced configurations though.
+ * *slots* : This parameter specifies the maximum number of jobs/blocks that the coaster scheduler will have running at any given time. On Beagle, this number will determine how many qsubs swift will submit for your run. Typical values range between 40 and 60 for large runs.
+ * *nodeGranularity* : Determines the number of nodes per job. It restricts the number of nodes in a job to a multiple of this value. The total number of workers will then be a multiple of jobsPerNode * nodeGranularity. For Beagle, jobsPerNode value is 24 corresponding to its 24 cores per node. 
  * *maxNodes* : Determines the maximum number of nodes a job must pack into its qsub. This parameter determines the largest single job that your run will submit.
  * *jobThrottle* : A factor that determines the number of tasks dispatched simultaneously. The intended number of simultaneous tasks must match the number of cores targeted. The number of tasks is calculated from the jobThrottle factor is as follows: