SEARS: Space efficient and reliable storage system in the cloud

Ying Li, Katherine Guo, Xin Wang, Emina Soljanin, Thomas Woo

Research output: Chapter in Book/Report/Conference proceedingConference contribution

1 Scopus citations

Abstract

Today's cloud storage services must offer storage reliability and fast data retrieval for large amount of data without sacrificing storage cost. We present SEARS, a cloud-based storage system which integrates erasure coding and data deduplication to support efficient and reliable data storage with fast user response time. With proper association of data to storage server clusters, SEARS provides flexible mixing of different configurations, suitable for real-Time and archival applications. Our prototype implementation of SEARS over Amazon EC2 shows that it outperforms existing storage systems in storage efficiency and file retrieval time. For 3 MB files, SEARS delivers retrieval time of 2.5 s compared to 7 s with existing systems.

Original languageEnglish (US)
Title of host publicationProceedings of the 40th Annual IEEE Conference on Local Computer Networks, LCN 2015
EditorsSalil Kanhere, Jens Tolle, Soumaya Cherkaoui
PublisherIEEE Computer Society
Pages418-421
Number of pages4
ISBN (Electronic)9781467367707
DOIs
StatePublished - Dec 24 2015
Externally publishedYes
Event2015 IEEE 40th Conference on Local Computer Networks, LCN 2015 - Clearwater Beach, United States
Duration: Oct 26 2015Oct 29 2015

Publication series

NameProceedings - Conference on Local Computer Networks, LCN
Volume26-29-October-2015

Other

Other2015 IEEE 40th Conference on Local Computer Networks, LCN 2015
Country/TerritoryUnited States
CityClearwater Beach
Period10/26/1510/29/15

All Science Journal Classification (ASJC) codes

  • Computer Networks and Communications
  • Hardware and Architecture

Keywords

  • cloud
  • deduplication
  • erasure coding
  • storage

Fingerprint

Dive into the research topics of 'SEARS: Space efficient and reliable storage system in the cloud'. Together they form a unique fingerprint.

Cite this