[Swift-commit] r6406 - in trunk/docs: merged/refmanual userguide
ketan at ci.uchicago.edu
ketan at ci.uchicago.edu
Mon Mar 25 14:22:57 CDT 2013
Author: ketan
Date: 2013-03-25 14:22:57 -0500 (Mon, 25 Mar 2013)
New Revision: 6406
Modified:
trunk/docs/merged/refmanual/grammar
trunk/docs/userguide/clustering
trunk/docs/userguide/coasters
trunk/docs/userguide/log-processing
trunk/docs/userguide/transformation_catalog
Log:
refinements and updations
Modified: trunk/docs/merged/refmanual/grammar
===================================================================
--- trunk/docs/merged/refmanual/grammar 2013-03-25 02:53:50 UTC (rev 6405)
+++ trunk/docs/merged/refmanual/grammar 2013-03-25 19:22:57 UTC (rev 6406)
@@ -394,7 +394,7 @@
;
----
-App procedure declaration
+App declaration
~~~~~~~~~~~~~~~~~~~~~~~~~
----
appproceduredecl returns [StringTemplate code=template("function")]
Modified: trunk/docs/userguide/clustering
===================================================================
--- trunk/docs/userguide/clustering 2013-03-25 02:53:50 UTC (rev 6405)
+++ trunk/docs/userguide/clustering 2013-03-25 19:22:57 UTC (rev 6406)
@@ -1,26 +1,24 @@
Clustering
----------
-Swift can group a number of short job submissions into a single larger
-job submission to minimize overhead involved in launching jobs (for
-example, caused by security negotiation and queuing delay). In general,
-CoG coasters should be used in preference to the clustering
-mechanism documented in this section.
+Swift can group a number of short job submissions into a single larger job
+submission to minimize overhead involved in launching jobs (for example, caused
+by security negotiation and queuing delay). In general, coasters should be used
+in preference to the clustering mechanism documented in this section.
By default, clustering is disabled. It can be activated by setting the
clustering.enabled property to true.
-A job is eligible for clustering if the GLOBUS::maxwalltime profile
-is specified in the tc.data entry for that job, and its value is
-less than the value of the clustering.min.time property.
+A job is eligible for clustering if the GLOBUS::maxwalltime profile is
+specified in the tc.data entry for that job, and its value is less than the
+value of the clustering.min.time property.
-Two or more jobs are considered compatible if they share the same site
-and do not have conflicting profiles (e.g. different values for the same
-environment variable).
+Two or more jobs are considered compatible if they share the same site and do
+not have conflicting profiles (e.g. different values for the same environment
+variable).
-When a submitted job is eligible for clustering, it will be put in a
-clustering queue rather than being submitted to a remote site. The
-clustering queue is processed at intervals specified by the
-clustering.queue.delay property. The
-processing of the clustering queue consists of selecting compatible jobs
-and grouping them into clusters whose maximum wall time does not exceed
-twice the value of the clustering.min.time property.
+When a submitted job is eligible for clustering, it will be put in a clustering
+queue rather than being submitted to a remote site. The queue is processed at
+intervals specified by the clustering.queue.delay property. The processing of
+the clustering queue consists of selecting compatible jobs and grouping them
+into clusters whose maximum wall time does not exceed twice the value of the
+clustering.min.time property.
Modified: trunk/docs/userguide/coasters
===================================================================
--- trunk/docs/userguide/coasters 2013-03-25 02:53:50 UTC (rev 6405)
+++ trunk/docs/userguide/coasters 2013-03-25 19:22:57 UTC (rev 6406)
@@ -106,6 +106,6 @@
The parameters provided in the coasters specification affect jobs submitted by Swift to the scheduling system.
----
-Jobs Submitted = slots X node_granularity X jobs_per_node
+Jobs Submitted = slots X jobsPerNode X nodeGranularity X maxNodes
----
Modified: trunk/docs/userguide/log-processing
===================================================================
--- trunk/docs/userguide/log-processing 2013-03-25 02:53:50 UTC (rev 6405)
+++ trunk/docs/userguide/log-processing 2013-03-25 19:22:57 UTC (rev 6406)
@@ -144,7 +144,9 @@
. _INFO ThrottleManager mem=113.54 MB, heap=482.88 MB, maxHeap=5.21 GB_
. _INFO ThrottleManager I maxBuffers=512, crtBuffers=0, allowedTransfers=256, active=0, suspended=0_
. _INFO PerformanceDiagnosticInputStream [MEM] Heap total: 482.88 MB, Heap used: 118.58 MB_
+Heap sizes for performance
. _INFO vdl:execute END_SUCCESS thread=0-8-0 tr=getsite_
+The job ended successfully
. _INFO WeightedHostScoreScheduler CONTACT_SELECTED host=localhost, score=99.854_
. _
Modified: trunk/docs/userguide/transformation_catalog
===================================================================
--- trunk/docs/userguide/transformation_catalog 2013-03-25 02:53:50 UTC (rev 6405)
+++ trunk/docs/userguide/transformation_catalog 2013-03-25 19:22:57 UTC (rev 6406)
@@ -1,18 +1,19 @@
-The Transformation Catalog - tc.data
-------------------------------------
+The Transformation Catalog - tc
+-------------------------------
The transformation catalog lists where application executables are
-located on remote sites.
+located on execution sites.
By default, the site catalog is stored in etc/tc.data. This path can
be overridden with the tc.file configuration property, either in the
Swift configuration file or on the command line.
-The format is one line per executable per site, with fields separated by
-tab or space.
+The format is one line per executable per site, with fields separated by space or tab.
Some example entries:
----
-localhost echo /bin/echo INSTALLED INTEL32::LINUX null
+localhost cat /bin/cat null null null
+localhost vasp /home/ketan/runvasp.sh null null null
+fusion echo /bin/echo INSTALLED INTEL32::LINUX null
TGUC touch /usr/bin/touch INSTALLED INTEL32::LINUX GLOBUS::maxwalltime="0:1"
----
@@ -24,11 +25,11 @@
The transformation name should correspond to the transformation name
used in a Swift script app procedure.
-The executable path should specify where the particular executable is
+The executable path should specify where the executable is
located on that site.
The installation status and platform fields are not used. Set them to
-INSTALLED and INTEL32::LINUX respectively.
+INSTALLED and INTEL32::LINUX respectively. Alternatively, they could be set to null.
The profiles field should be set to null if no profile entries are to
be specified.
@@ -39,6 +40,7 @@
This can be accomplished using *env* in the profile entry. For example,
the following application sets an environment variable called R_LIBS to
/home/user/R_libs.
+
-----
localhost R /usr/bin/R INSTALLED INTEL32::LINUX env::R_LIBS=/home/user/r_libs
-----
More information about the Swift-commit
mailing list