Changes between Version 36 and Version 37 of FGBI


Ignore:
Timestamp:
10/06/11 23:03:20 (13 years ago)
Author:
lvpeng
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • FGBI

    v36 v37  
    5050
    5151Figures 2a, 2b, 2c, and 2d show the type I downtime com-
    52 parison among [wiki:FGBI FGBI], [wiki:LLM LLM], and [http://nss.cs.ubc.ca/remus/ Remus] mechanisms under Apache, [http://www.nas.nasa.gov/Resources/Software/npb.html NPB-EP],
     52parison among [wiki:FGBI FGBI], [wiki:LLM LLM], and [http://nss.cs.ubc.ca/remus/ Remus] mechanisms under [http://httpd.apache.org/ Apache], [http://www.nas.nasa.gov/Resources/Software/npb.html NPB-EP],
    5353SPECweb, and SPECsys applications, respectively. The block size used in all
    5454experiments is 64 bytes. For [http://nss.cs.ubc.ca/remus/ Remus] and [wiki:FGBI FGBI], the checkpointing period is the
    … …  
    5858buffer frequency of [wiki:LLM LLM], we ensure the fairness of the comparison. We observe
    5959that Figures 2a and 2b show a reverse relationship between [wiki:FGBI FGBI] and [wiki:LLM LLM].
    60 Under Apache (Figure 2a), the network load is high but system updates are
     60Under [http://httpd.apache.org/ Apache] (Figure 2a), the network load is high but system updates are
    6161rare. Therefore, [wiki:LLM LLM] performs better than [wiki:FGBI FGBI], since it uses a much higher
    6262frequency to migrate the network service requests. On the other hand, when
    … …  
    7373rather than Figure 2a. In conclusion, compared with [wiki:LLM LLM], [wiki:FGBI FGBI] reduces the
    7474downtime by as much as 77%. Moreover, compared with [http://nss.cs.ubc.ca/remus/ Remus], [wiki:FGBI FGBI] yields a
    75 shorter downtime, by as much as 31% under Apache, 45% under [http://www.nas.nasa.gov/Resources/Software/npb.html NPB-EP], 39%
     75shorter downtime, by as much as 31% under [http://httpd.apache.org/ Apache], 45% under [http://www.nas.nasa.gov/Resources/Software/npb.html NPB-EP], 39%
    7676under SPECweb, and 35% under SPECsys.
    7777
    … …  
    8989by its low memory transfer frequency. Therefore in this case [wiki:FGBI FGBI] achieves a
    9090much lower downtime than [http://nss.cs.ubc.ca/remus/ Remus] (reduce more than 70%) and [wiki:LLM LLM] (more
    91 than 90%). (3) When running Apache application, the memory update is not so
     91than 90%). (3) When running [http://httpd.apache.org/ Apache] application, the memory update is not so
    9292much as that when running [http://www.nas.nasa.gov/Resources/Software/npb.html NPB], but the memory update is definitely more than
    9393"idle" run. The downtime results shows [wiki:FGBI FGBI] still outperforms both [http://nss.cs.ubc.ca/remus/ Remus] and
    … …  
    100100
    101101Figure 3a shows the overhead during VM migration. The figure compares the
    102 applications' runtime with and without migration, under Apache, SPECweb,
     102applications' runtime with and without migration, under [http://httpd.apache.org/ Apache], SPECweb,
    103103[http://www.nas.nasa.gov/Resources/Software/npb.html NPB-EP], and SPECsys, with the size of the fine-grained blocks varies from 64
    104104bytes to 128 bytes and 256 bytes. We observe that in all cases the overhead is
    105 low, no more than 13% (Apache with 64 bytes block). As we discuss in Section 3,
     105low, no more than 13% ([http://httpd.apache.org/ Apache] with 64 bytes block). As we discuss in Section 3,
    106106the smaller the block size that [wiki:FGBI FGBI] chooses, the greater is the memory overhead
    107107that it introduces. In our experiments, the smaller block size that we chose is 64