Changes between Version 51 and Version 52 of VDEchp


Ignore:
Timestamp:
10/13/11 16:07:28 (13 years ago)
Author:
lvpeng
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • VDEchp

    v51 v52  
    3030<center>
    3131<img style="border:0px;" src="/trac/fgbi/raw-attachment/wiki/VDEchp/figure2.jpg">
    32 <h4>Figure 2. The definition of the global checkpoint.
    33 </h4> 
     32<h4>Figure 2. The definition of the global checkpoint.</h4> 
    3433</center>
    3534}}}
    … …  
    5352=== Downtime Evaluation for Solo VM ===
    5453[[Image(table1.jpg)]]
    55 
    56              Table 1. Solo VM downtime comparison.
     54{{{
     55#!html
     56<center>
     57<img style="border:0px;" src="/trac/fgbi/raw-attachment/wiki/VDEchp/table1.jpg">
     58<h4>Figure 3. VDE downtime under Apache and NPB benchmarks.</h4> 
     59</center>
     60}}}
    5761
    5862Table I shows the downtime results under different mechanisms. We compare [wiki:VDEchp VDEchp] with [http://nss.cs.ubc.ca/remus/ Remus] and the [http://friends.cs.purdue.edu/dokuwiki/doku.php?id=vnsnap VNsnap]-memory daemon, under the same checkpoint interval. We measure the downtime of all three mechanisms, with the same VM (with 512MB of RAM), for three cases: a) when the VM is idle, b) when the VM runs the [http://www.nas.nasa.gov/Resources/Software/npb.html NPB-EP] benchmark program, and c) when the VM runs the [http://httpd.apache.org/ Apache] web server workload.
    … …  
    6973
    7074=== VDE Downtime ===
    71 [[Image(figure3.jpg)]]
     75{{{
     76#!html
     77<center>
     78<img style="border:0px;" src="/trac/fgbi/raw-attachment/wiki/VDEchp/figure3.jpg">
     79<h4>Table 1. Solo VM downtime comparison.</h4> 
     80</center>
     81}}}
    7282
    73             Figure 3. VDE downtime under [http://httpd.apache.org/ Apache] and [http://www.nas.nasa.gov/Resources/Software/npb.html NPB] benchmarks.
    74 
     83           
    7584The VDE downtime is the time from when the failure was detected in the VDE until the entire VDE resumes from the last globally consistent checkpoint. We conducted experiments to measure the downtime. To induce failures in the VDE, we developed an application program that causes a segmentation failure after executing for a while. This program is launched on several VMs to generate a failure while the distributed application workload is running in the VDE. The protected VDE is then rolled back to the last globally consistent checkpoint. We use the [http://www.nas.nasa.gov/Resources/Software/npb.html NPB-EP] program (MPI task in the VDE) and the [http://httpd.apache.org/ Apache] web server benchmark as the distributed workload on the protected VMs.
    7685