Changes between Version 5 and Version 6 of ThroughputDemo_20091104

Timestamp:

Nov 6, 2009, 10:59:54 AM (17 years ago)

Author:

eugene

Comment:

--

ThroughputDemo_20091104

@@ -122 +122 @@
 
  * there are a number of chipRuns that have not finished: 37 exposures
-are still pending.  This is basically because of point 2:
+ are still pending.  This is basically because of point 2:
 
  * ipp014 is unhappy: it is not so unhappy that it has been kicked out
-of nebulous, but files on it are giving I/O errors.  The failing chips
-are being caused by this, but coupled to a lingering nebulous error:
-the rules are forcing nebulous to return the ipp014 instance rather
-than randomize among the instances.  i'm going to reboot ipp014 and
-kick it out of nebulous for now.
+ of nebulous, but files on it are giving I/O errors.  The failing chips
+ are being caused by this, but coupled to a lingering nebulous error:
+ the rules are forcing nebulous to return the ipp014 instance rather
+ than randomize among the instances.  i'm going to reboot ipp014 and
+ kick it out of nebulous for now.
 
 I'm attaching a snapshot of the ganglia load for the past 24 hours.
@@ -142 +142 @@
 or because of poor data distribution.  this is something we need to
 investigate.
+
+[[Image(ganglia-throughput-20091104.png)]]
 
 === update ===
@@ -171 +173 @@
 yesterday.  You can see that we start at about the 13/bin rate for the
 first period of the test, during which I had jobs running on 137
-nodes[1].  You can see the period around 6pm last night when I crashed
+nodes^*^.  You can see the period around 6pm last night when I crashed
 pantasks and waited a bit to restart the system.  Then you can see the
 rate goes up to about 20/bin for the last part of the test, during
@@ -194 +196 @@
 [[Image(throughput.20091104.camera.png)]]
 
-[[Image(ganglia-throughput-20091104.png)]]
-
-[1] -- roughly : ipp005 and ipp039 came in and out of the list at
+^*^ roughly : ipp005 and ipp039 came in and out of the list at
 different times.