File Download
There are no files associated with this item.
Supplementary
-
Citations:
- Appears in Collections:
Conference Paper: PLOVER: Fast, Multi-core Scalable Virtual Machine Fault-tolerance
Title | PLOVER: Fast, Multi-core Scalable Virtual Machine Fault-tolerance |
---|---|
Authors | |
Issue Date | 2018 |
Publisher | USENIX Association. |
Citation | Proceedings of the 15th USENIX Symposium on Networked Systems Design and Implementation 2018 (NSDI '18), Renton, WA, USA, 9–11 April 2018, p. 483-499 How to Cite? |
Abstract | Cloud computing enables a vast deployment of online services in virtualized infrastructures, making it crucial to provide fast fault-tolerance for virtual machines (VM). Unfortunately, despite much effort, achieving fast and multi-core scalable VM fault-tolerance is still an open problem. A main reason is that the dominant primarybackup approach (e.g., REMUS) transfers an excessive amount of memory pages, all of them, updated by a service replicated on the primary VM and the backup VM. This approach makes the two VMs identical but greatly degrades the performance of services.
State machine replication (SMR) enforces the same total order of inputs for a service replicated across physical hosts. This makes most updated memory pages across hosts the same and they do not need to be transferred. We present Virtualized SMR (VSMR), a new approach to tackle this open problem. VSMR enforces the same order of inputs for a VM replicated across hosts. It uses commodity hardware to efficiently compute updated page hashes and to compare them across replicas. Therefore, VSMR can efficiently enforce identical VMs by transferring only divergent pages. An extensive evaluation on PLOVER, the first VSMR system, shows that PLOVER’s throughput on multi-core is 2.2X to 3.8X higher than three popular primary-backup systems. Meanwhile, PLOVER consumed 9.2X less network bandwidth than both of them. PLOVER’s source code and raw results are released on github.com/ hku-systems/plover. |
Persistent Identifier | http://hdl.handle.net/10722/260640 |
ISBN |
DC Field | Value | Language |
---|---|---|
dc.contributor.author | Wang, C | - |
dc.contributor.author | Chen, XS | - |
dc.contributor.author | Jia, WW | - |
dc.contributor.author | Li, BX | - |
dc.contributor.author | Qiu, HR | - |
dc.contributor.author | Zhao, SX | - |
dc.contributor.author | Cui, H | - |
dc.date.accessioned | 2018-09-14T08:44:55Z | - |
dc.date.available | 2018-09-14T08:44:55Z | - |
dc.date.issued | 2018 | - |
dc.identifier.citation | Proceedings of the 15th USENIX Symposium on Networked Systems Design and Implementation 2018 (NSDI '18), Renton, WA, USA, 9–11 April 2018, p. 483-499 | - |
dc.identifier.isbn | 978-1-931971-43-0 | - |
dc.identifier.uri | http://hdl.handle.net/10722/260640 | - |
dc.description.abstract | Cloud computing enables a vast deployment of online services in virtualized infrastructures, making it crucial to provide fast fault-tolerance for virtual machines (VM). Unfortunately, despite much effort, achieving fast and multi-core scalable VM fault-tolerance is still an open problem. A main reason is that the dominant primarybackup approach (e.g., REMUS) transfers an excessive amount of memory pages, all of them, updated by a service replicated on the primary VM and the backup VM. This approach makes the two VMs identical but greatly degrades the performance of services. State machine replication (SMR) enforces the same total order of inputs for a service replicated across physical hosts. This makes most updated memory pages across hosts the same and they do not need to be transferred. We present Virtualized SMR (VSMR), a new approach to tackle this open problem. VSMR enforces the same order of inputs for a VM replicated across hosts. It uses commodity hardware to efficiently compute updated page hashes and to compare them across replicas. Therefore, VSMR can efficiently enforce identical VMs by transferring only divergent pages. An extensive evaluation on PLOVER, the first VSMR system, shows that PLOVER’s throughput on multi-core is 2.2X to 3.8X higher than three popular primary-backup systems. Meanwhile, PLOVER consumed 9.2X less network bandwidth than both of them. PLOVER’s source code and raw results are released on github.com/ hku-systems/plover. | - |
dc.language | eng | - |
dc.publisher | USENIX Association. | - |
dc.relation.ispartof | Proceedings of the 15th USENIX Symposium on Networked Systems Design and Implementation 2018 (NSDI '18) | - |
dc.title | PLOVER: Fast, Multi-core Scalable Virtual Machine Fault-tolerance | - |
dc.type | Conference_Paper | - |
dc.identifier.email | Cui, H: heming@hku.hk | - |
dc.identifier.authority | Cui, H=rp02008 | - |
dc.description.nature | link_to_subscribed_fulltext | - |
dc.identifier.hkuros | 291705 | - |
dc.identifier.spage | 483 | - |
dc.identifier.epage | 499 | - |
dc.publisher.place | United States | - |