[Swift-commit] r4405 - www/cookbook

Sun Apr 24 22:43:39 CDT 2011

Author: ketan
Date: 2011-04-24 22:43:39 -0500 (Sun, 24 Apr 2011)
New Revision: 4405

Modified:
   www/cookbook/cookbook-asciidoc.html
Log:
 

Modified: www/cookbook/cookbook-asciidoc.html
===================================================================

--- www/cookbook/cookbook-asciidoc.html	2011-04-25 03:42:59 UTC (rev 4404)
+++ www/cookbook/cookbook-asciidoc.html	2011-04-25 03:43:39 UTC (rev 4405)
@@ -603,14 +603,14 @@
 <div class="sectionbody">
 <div class="sect2">
 <h3 id="_installation">2.1. Installation</h3>
-<div class="paragraph"><p>Installation instructions</p></div>
+<div class="paragraph"><p>This section takes you through the installation of the Swift system on your
+computer. We will start with the prerequisites as explained in the subsequent
+section.</p></div>
 <div class="sect3">
-<h4 id="_prerequisites">2.1.1. prerequisites</h4>
-<div class="paragraph"><p>Check your Java
-Swift is a Java application. Make sure you’re running Java 5 or higher. You
-can make sure you have Java in your $HOME/.soft file and the softenv system
-(<a href="http://www.ci.uchicago.edu/wiki/bin/view/Resources/Softenv">http://www.ci.uchicago.edu/wiki/bin/view/Resources/Softenv</a>) will set it up
-for you. To run Java 6:</p></div>
+<h4 id="_prerequisites">2.1.1. Prerequisites</h4>
+<div class="paragraph"><div class="title">Check your Java</div><p>Swift is a Java application. Make sure you are running Java version 5 or higher. You
+can make sure you have Java in your $PATH (or $HOME/.soft file depending upon your environment)</p></div>
+<div class="paragraph"><p>Following are the possible ways to detect and run Java:</p></div>
 <div class="listingblock">
 <div class="content">
 <pre><tt>$ grep java $HOME/.soft
@@ -623,11 +623,9 @@
 Java(TM) SE Runtime Environment (build 1.6.0_11-b03)
 Java HotSpot(TM) 64-Bit Server VM (build 11.0-b16, mixed mode)</tt></pre>
 </div></div>
-<div class="paragraph"><p>Setting up to run Swift
-This is simple. We’ll be using a version of the Swift stable SVN branch,
-compiled for this class.  Make sure you have a suitable Java set up. The examples were tested with
-Java version 1.6 Make sure you don’t already have Swift in your PATH. If you do, remove it,
-or remove any +swift or @swift lines from your $HOME/.soft file. Then do: PATH=$PATH:/home/wilde/bigdata/swift/bin
+<div class="paragraph"><div class="title">Setting up to run Swift</div><p>This is simple. We will be using a pre-compiled version of Swift that can be downloaded from the following location: <a href="http://www.ci.uchicago.edu/swift/packages/swift-0.92.1.tar.gz">http://www.ci.uchicago.edu/swift/packages/swift-0.92.1.tar.gz</a>
+. The examples were tested with Java version 1.6 Make sure you don’t already have Swift in your PATH. If you do, remove it,
+or remove any +swift or @swift lines from your $HOME/.soft or $HOME/.bash_profile file. Then do: PATH=$PATH:/home/wilde/bigdata/swift/bin
  Do NOT set SWIFT_HOME or CLASSPATH in your environment unless you fully
 understand how these will affect Swift’s execution</p></div>
 </div>
@@ -823,7 +821,37 @@
 <div class="paragraph"><p>Also includes a description of Swift inputs and outputs.</p></div>
 </div>
 <div class="sect2">
-<h3 id="_resuming_a_stopped_or_crashed_swift_run">2.6. Resuming a stopped or crashed Swift Run</h3>
+<h3 id="_what_if_swift_hangs">2.6. What if Swift hangs</h3>
+<div class="paragraph"><p>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 <em>hang-checker</em> chips in and resolves the situation.</p></div>
+<div class="olist arabic"><ol class="arabic">
+<li>
+<p>
+how to use the information to identify and correct the deadlock.
+</p>
+</li>
+<li>
+<p>
+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?
+</p>
+</li>
+<li>
+<p>
+The current Hang Checker output is actually <strong>very</strong> 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
+</p>
+</li>
+</ol></div>
+</div>
+<div class="sect2">
+<h3 id="_resuming_a_stopped_or_crashed_swift_run">2.7. Resuming a stopped or crashed Swift Run</h3>
 <div class="paragraph"><p>I had a .rlog file from a Swift run that ran out of time. I kicked it off
 using the -resume flag described in section 16.2 of the Swift User Guide and
 it picked up where it left off. Then I killed it because I wanted to make
@@ -924,7 +952,7 @@
 run\]</tt></p></div>
 </div>
 <div class="sect2">
-<h3 id="_passing_an_array_to_swift">2.7. Passing an array to swift?</h3>
+<h3 id="_passing_an_array_to_swift">2.8. Passing an array to swift?</h3>
 <div class="olist arabic"><ol class="arabic">
 <li>
 <p>
@@ -1072,8 +1100,43 @@
 Its a very interesting question, and a hard but critically important one to
 answer to make usage simpler.</tt></pre>
 </div></div>
-<div class="sect2">
-<h3 id="_debugging_swift">4.1. Debugging Swift</h3>
+<div class="paragraph"><p>For Advanced Users or How do I fine tune coasters to target specific execution
+environment</p></div>
+<div class="listingblock">
+<div class="content">
+<pre><tt>//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
+//~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+//
+//Manual
+//^^^^^^^
+//Todo
+//
+//Passive
+//^^^^^^^^
+//Todo
+//
+//Persistent
+//^^^^^^^^^^^
+//Todo
+//
+//Summary of Differences Between different Coaster types
+//~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+//A tabular representations of highlights of different coaster setups
+//
+//
+//Data Management
+//
+
+Debugging Swift</tt></pre>
+</div></div>
 <div class="paragraph"><p>Swift errors are logged in several places:</p></div>
 <div class="olist arabic"><ol class="arabic">
 <li>
@@ -1109,9 +1172,8 @@
 </p>
 </li>
 </ol></div>
-</div>
 <div class="sect2">
-<h3 id="_problem_reporting">4.2. Problem Reporting</h3>
+<h3 id="_problem_reporting">4.1. Problem Reporting</h3>
 <div class="paragraph"><p>When reporting problems to <a href="mailto:swift-user at ci.uchicago.edu">swift-user at ci.uchicago.edu</a>, please attach the
 following files and information:</p></div>
 <div class="olist arabic"><ol class="arabic">
@@ -1175,7 +1237,7 @@
 <div id="footer">
 <div id="footer-text">
 Version 0.92<br />
-Last updated 2011-04-15 20:43:12 CDT
+Last updated 2011-04-23 20:51:22 CDT
 </div>
 </div>
 </body>


