Demonstration venue · read-only. Every page can be browsed; the buttons that would change it are switched off. Create an account to run TaxoReview on your own data. A simulation from public publication records: the people listed were not invited and did not agree to review.
? Tutorial for this page

Gopalakrishna Holla

dblp:168/2807 · DBLP profile ↗
← Back
1ranked-venue papers
0as first author
0since 2021 · last 2016
—ORCID · none

Domains — the database's venue-derived domains; a paper can count in several

Databases, data management, data science and information retrieval · 1

Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.

Computer architecture, parallel and distributed computing, and storage systems
1 paper
Storage systems · 46% Distributed systems · 46% Cloud and datacenter computing · 7%

Topics — the 4 heaviest of 5, each with the papers that count most for it

TopicWeightPapersLastEvidence papers
Distributed systems › replication › replica control
asynchronous replication
0.212016
Ambry: LinkedIn's Scalable Geo-Distributed Object Store · SIGMOD Conference 2016
Storage systems › distributed storage
geo-distributed storage
0.212016
Ambry: LinkedIn's Scalable Geo-Distributed Object Store · SIGMOD Conference 2016
Storage systems
object storage
0.212016
Ambry: LinkedIn's Scalable Geo-Distributed Object Store · SIGMOD Conference 2016
Distributed systems
replication
0.212016
Ambry: LinkedIn's Scalable Geo-Distributed Object Store · SIGMOD Conference 2016

Methods — techniques the papers use, named apart from their topics

zero-cost failure detection · 0.2rebalancing · 0.2logical blob grouping · 0.2OS caching · 0.2
YearPublicationVenuePosition
2016 Ambry: LinkedIn's Scalable Geo-Distributed Object Store
abstract
The infrastructure beneath a worldwide social network has to continually serve billions of variable-sized media objects such as photos, videos, and audio clips. These objects must be stored and served with low latency and high throughput by a system that is geo-distributed, highly scalable, and load-balanced. Existing file systems and object stores face several challenges when serving such large objects. We present Ambry, a production-quality system for storing large immutable data (called blobs). Ambry is designed in a decentralized way and leverages techniques such as logical blob grouping, asynchronous replication, rebalancing mechanisms, zero-cost failure detection, and OS caching. Ambry has been running in LinkedIn's production environment for the past 2 years, serving up to 10K requests per second across more than 400 million users. Our experimental evaluation reveals that Ambry offers high efficiency (utilizing up to 88% of the network bandwidth), low latency (less than 50 ms latency for a 1 MB object), and load balancing (improving imbalance of request rate among disks by 8x-10x).
Shadi A. Noghabi, Sriram Subramanian, Priyesh Narayanan, Sivabalan Narayanan, Gopalakrishna Holla, Mammad Zadeh, Tianwei Li, Indranil Gupta, Roy H. Campbell
SIGMOD Conference5