Managing Capacity
summary
LinkedIn describes a capacity system serving 500 million members across 95,000 servers and 29 MW, with Hadoop at 170 PB, Espresso holding 4.2 PB across 237 databases, and 2 trillion events flowing through Kafka. Capacity methods use metrics every 5 minutes, 98th/97th-percentile quarterly snapshots, buffers, and standard hardware sizing. Built tools include Kafka capacity tool (fabric → topic partition visibility), Dr. Elephant for job tuning, and ReWinder/Sizes for historical and HDFS growth tracking.
AI-written summary · about
chapters (5)
- 0:00Introduction
- 1:45LinkedIn in 2010
- 8:29Capacity Planning
- 12:16Capacity Management
- 15:30Capacity Planning Hadoop
related talks
01h 00mPutting Apache Kafka to Use
29mCapacity Planning with the Universal Scalability Law
50mApache Kafka + Zookeeper = 3.5 Million Writes Per Second by Design
05mPREVIEW: 1 Day, 1 Data Hub, 100 Billion Messages
38mData Pipeline with Apache Kafka
32mScaling your Kafka streaming pipeline....
32mShould you read Kafka as a stream or in batch? Should you even care?
38mKafka Message Broker Under High Load
