[Swift-commit] r4382 - in www/cookbook: . figures

[ketan at ci.uchicago.edu]

Author: ketan
Date: 2011-04-16 21:47:17 -0500 (Sat, 16 Apr 2011)
New Revision: 4382

Added:
   www/cookbook/figures/
   www/cookbook/figures/coaster_setup.png
Modified:
   www/cookbook/cookbook-asciidoc.html
   www/cookbook/cookbook-asciidoc.txt
Log:


Modified: www/cookbook/cookbook-asciidoc.html
===================================================================
--- www/cookbook/cookbook-asciidoc.html	2011-04-16 01:02:06 UTC (rev 4381)
+++ www/cookbook/cookbook-asciidoc.html	2011-04-17 02:47:17 UTC (rev 4382)
@@ -967,7 +967,16 @@
 will get fast prioritized execution. Good for small tests</p></div>
 </div>
 <div class="sect2">
-<h3 id="_bionimbus">3.2. Bionimbus</h3>
+<h3 id="_osg">3.2. OSG</h3>
+<div class="imageblock">
+<div class="content">
+<img src="figures/coaster_setup.png" alt="Coaster setup" />
+</div>
+<div class="title">Figure 1. Coaster setup on OSG</div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_bionimbus">3.3. Bionimbus</h3>
 <div class="paragraph"><p>Swift on Bionimbus
 .very important to read this</p></div>
 <div class="paragraph"><p>contains information on how to connect back to gateway from virtual machines
@@ -1166,7 +1175,7 @@
 <div id="footer">
 <div id="footer-text">
 Version 0.92<br />
-Last updated 2011-04-15 19:20:00 CDT
+Last updated 2011-04-15 20:43:12 CDT
 </div>
 </div>
 </body>

Modified: www/cookbook/cookbook-asciidoc.txt
===================================================================
--- www/cookbook/cookbook-asciidoc.txt	2011-04-16 01:02:06 UTC (rev 4381)
+++ www/cookbook/cookbook-asciidoc.txt	2011-04-17 02:47:17 UTC (rev 4382)
@@ -253,7 +253,26 @@
 
 Also includes a description of Swift inputs and outputs.
 
+What if Swift hangs
+~~~~~~~~~~~~~~~~~~~
+Owing to its highly multithreaded architecture it is often the case that the
+underlying java virtual machine gets into deadlock situations or Swift hangs
+because of other complications in its threaded operations. Under such
+situations, Swift _hang-checker_ chips in and resolves the situation.
 
+. how to use the information to identify and correct the deadlock.
+
+. How close to the Swift source code can we make the hang-checker messages, so that the user can relate it to Swift functions, expressions, and ideally source code lines?
+
+. The current Hang Checker output is actually *very* nice and useful already:
+Registered futures:
+Rupture[] rups  Closed, 1 elements, 0 listeners
+Variation vars - Closed, no listeners
+SgtDim sub - Open, 1 listeners
+string site  Closed, no listeners
+Variation[] vars  Closed, 72 elements, 0 listeners
+
+
 Resuming a stopped or crashed Swift Run
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
@@ -344,6 +363,7 @@
 +swift -resume ftdock-[id].0.rlog \[rest of the exact command line from initial
 run\]+
 
+
 Passing an array to swift?
 ~~~~~~~~~~~~~~~~~~~~~~~~~~
 . you can write the array to a file and read in in swift using
@@ -386,8 +406,10 @@
 //~~~~
 //Swift on PADS 
 //
-//OSG
-//~~~
+OSG
+~~~
+.Coaster setup on OSG
+image::figures/coaster_setup.png[Coaster setup]
 //Swift on OSG 
 //
 Bionimbus
@@ -516,11 +538,17 @@
 //
 //
 //
-//For Advanced Users
-//~~~~~~~~~~~~~~~~~~~
+For Advanced Users or How do I fine tune coasters to target specific execution
+environment
+~~~~~~~~~~~~~~~~~~~
 //Coasters for advanced users. Getting your hands dirty.
-//
-//
+
+. One of the main reason that one would initially deviate from coaster defaults
+into more complex pool entries is to force jobs to fit into some site-imposed
+constraint. For instance a typical submission to the experimental queue requires a user to
+request upto 3 nodes for under 1 hour. This setup could be achieved with a
+careful tuning of coaters parameters.
+
 //How to run Swift under different Coasters configurations
 //~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 //

Added: www/cookbook/figures/coaster_setup.png
===================================================================
(Binary files differ)


Property changes on: www/cookbook/figures/coaster_setup.png
___________________________________________________________________
Name: svn:mime-type
   + application/octet-stream