[Saga-devel] saga-projects SVN commit 889: /papers/clouds/

[sjha at cct.lsu.edu]

User: sjha
Date: 2009/01/27 04:46 PM

Modified:
 /papers/clouds/
  saga_cloud_interop.tex

Log:
 some minor additions

File Changes:

Directory: /papers/clouds/
==========================

File [modified]: saga_cloud_interop.tex
Delta lines: +5 -21
===================================================================
--- papers/clouds/saga_cloud_interop.tex	2009-01-27 21:24:22 UTC (rev 888)
+++ papers/clouds/saga_cloud_interop.tex	2009-01-27 22:46:52 UTC (rev 889)
@@ -1229,29 +1229,9 @@
   0 & 1 (4) & 10 &  11.3 & 8.6 \\
   0 & 1 (4) & 100 & 16.2 & 8.7 \\ 
   \hline \hline
-%   TeraGrid &  AWS &   (MB)  & (sec) & (sec)  \\
-%   \hline
-%   6 & 0 & 10   &  153.5 & 103.0  \\
-%   10 & 0 & 10  &  433.0  & 299.0 \\
-%   \hline 
-%   0 & 1 & 10 & 18.5 & 7.7 \\
-%   0 & 2 & 10 &  49.2 & 27.0 \\
-%   0 & 3 & 10 & 75.9 & 59.6 \\
-%   0 & 4 & 10 & 169.8 & 106.3 \\
-%   \hline 
-%   2 & 2 & 10 & 54.7 & 35.0 \\
-%   3 & 3 & 10 & 135.7 & 106.9 \\
-%   4 & 4 &10 & 188.0 & 135.2 \\
-%   10 & 10 & 10 & 1037.5 & 830.0 \\
-%   \hline
-%   \hline 
-%   0 & 2 & 100 & 62.1 & 27.8 \\
-%   0 & 10 & 100 &  845.0 & 632.0 \\
-%   1 & 1 & 100 & 29.04 & 9.79 \\
-%   \hline \hline
 \end{tabular}
 \upp
-\caption{Performance data for different configurations of worker placements. The master is always on a desktop, with the choice of workers placed on either Clouds or on the TeraGrid (QueenBee). The configurations can be classified as of three types -- all workers on EC2, all workers on the TeraGrid and workers divied between the TeraGrid and EC2. Every worker is assigned to a unique  VM. It is interesting to note the significant spawning times, and its dependence on the number of VM.}
+\caption{Performance data for different configurations of worker placements. The master is always on a desktop, with the choice of workers placed on either Clouds or on the TeraGrid (QueenBee). The configurations can be classified as of three types -- all workers on EC2, all workers on the TeraGrid and workers divied between the TeraGrid and EC2. Every worker is assigned to a unique  VM. It is interesting to note the significant spawning times, and its dependence on the number of VM. Spawning time is without instantiation.}
 \label{stuff}
 \upp
 \upp
@@ -1318,6 +1298,10 @@
 \subsubsection*{Challenges: Network, System Configuration and
   Experiment Details}
 
+Images get corrupted if mapreduce does not terminate properly
+
+Networking issues.
+
 All this is new technology, hence makes sense to try to list some of
 the challenges we faced.