You are viewing content from a past/completed QCon -

Presentation: Capacity Planning for Crypto Mania

Track: Production Readiness: Building Resilient Systems

Location: Pacific LMNO

Duration: 10:35am - 11:25am

Day of week: Wednesday

Slides: Download Slides

Level: Intermediate

Persona: Architect, Chaos/Resiliency/SRE, Technical Engineering Manager

This presentation is now available to view on

Watch video with transcript

What You’ll Learn

  • Learn about how Coinbase had to deal with the Cryptocurrency spikes of 2017.

  • Hear about capacity planning has been changed and affected by the lessons the company learned last year.

  • Hear about the tension between synthetic traffic and playback for load testing, and then understand more about how Coinbase reasons about the choices they make for planning.


Over the course of 2017, Coinbase experienced exponential user and trading volume growth, which in turn led to periods of website instability and downtime. During this period, we saw our systems perform at the very edge of their capacity which inspired important capacity and performance improvements. Since then we have sought new ways to push our systems to their limits so that we can be sure that we are focusing our energy on the right projects. 

Come to hear how Coinbase engineers are applying lessons from these experiences to create new tools and techniques for capacity planning to prepare for future waves of cryptocurrency enthusiasm.


What's the focus of the work that you do today?


Jordan: We’re on the Reliability Team at Coinbase. It was formed in response to the crazy spike of scaling challenges around 2017 with Cryptocurrency. The work is focused on traditional SRE topics of monitoring and instrumentation. We act as consultants for other mostly feature-focused teams. For example, we embed in teams to make sure that they're putting in place best practices of shipping scalable versions of the features they are implementing, or we make sure long-term plans are in place for things like capacity planning, alerting, and PagerDuty. Capacity planning is a big part of our day-to-day work now so we think it’s a great fit for the Production Readiness track.


The spike that you're talking about is bitcoin basically going from $6,000 to $18,000 in a really short period of time. Is that right?


Jordan: Yeah. That's the story of cryptocurrency so far. It is these crazy (almost overnight) run ups in price that put lots of stress on everyone’s systems.


What does this spike mean in terms a software engineer can relate too? What does a $6,000 to $18,000 price jump mean to your systems?


Luke: It's important to make clear that the prices are very important. They correlate really closely to the amount of traffic we see. However, they're not really relevant in terms of our scaling challenges. The price being $4,000 versus $20,000 doesn't change the way we operate at the ground level (although it may mean that there's a lot more traffic due to increased interest).

Luke: In terms of how a developer would understand the load, we grew traffic by 60x between our normal load at the beginning of 2017 and our peak traffic in December. We went from regularly around 30,000 requests per minute on average to peaks in December of 1.5 million requests per minute. A lot of little things we didn't expect to have happen to us when we joined this company happened. Things like, we were the number one app in the App Store for a week. That's a big part of the talk. It’s the idea it could happen to you.

Luke: And to add a little bit to what Jordan said, this new team formed over 2018, but in 2017, we did all these actions that this team is doing now. We just did them under the gun. We built capacity planning frameworks in an afternoon. Then we built them again next weekend, and the weekend after. So we learned a lot of lessons which have been super valuable. We’ve had the chance now to step back and plan things a bit differently. We’re going to share some of these lessons.


So now that the load is off, how did the events of 2018 change how you all plan?


Luke: We started with a question. If we were to get hit with the same amount of traffic that we were able to withstand in December, how confident are we that we would be able to withstand it? That's why we had to double down on capacity planning. We had to get this going correctly if we were going to be able to reliably answer that question. We've double down on capacity planning.

Luke: There are big questions here. For example, do you need to actually simulate 1.5 million requests per minute for your tests? Are there other approaches? How perfectly do you need to simulate the load in terms of user traffic? There is a major tension between simulation testing and replay testing. How are we approaching them? What are the pros and cons of both? These are challenges that we've had to approach this year.

Luke: We feel like we're starting to get a feel for how this actually looks in a real day-to-day environment.

Jordan: And on that note, I think when a lot of people talk about capacity planning, it’s sometimes with this air of it being a somewhat one-time, slightly academic exercise. One of the themes that I want to make sure we get into our talk is here's how you practice capacity planning on an ongoing basis in a real organization that's operating on a similar scale to where we were at the end of 2017.

Jordan: We don't necessarily have a single expert in load testing and capacity planning, but it's something that is important to acknowledge and get done. I have a little comment here in my notes that says “I want this talk to be the one that I wish I had seen exactly one year ago, and I want you to address me as a somewhat experienced engineer in a generalist sense facing something similar.”


Can you pick one example of something you might discuss that will be in the talk about something somebody may be able to apply?


Jordan: I think one thing we're going to talk specifically about is load testing our database. The database was one of our biggest challenges. That specific bottleneck is something I spent time building specific tooling on. I'd like to give some actual hands-on details about how that tool works, what it does, and then give some takeaways that are general learnings about how you load test a database in isolation.

Jordan: We’ll also touch on this tension between synthetic traffic and playback. Specifically addressing how you honor all the things that you need to achieve while still walking that line between the two.

Luke: On simulation testing, I'm hoping people can walk away thinking, “Oh, that's not that bad, to be able to do those types of things.”

Luke: I hope the message we're giving people is that “These broad concepts can be applied to my environment, and it's approachable.”

Speaker: Jordan Sitkin

Software Engineer @coinbase

Speaker: Luke Demi

Software Engineer @coinbase

Luke Demi is a software engineer obsessed with delivering reliability. After four years of scalability and developer productivity at Coinbase he is now a founding member of the newly formed SRE team at DoorDash.

Find Luke Demi at

Last Year's Tracks

  • Monday, 16 November

  • Paths to Production: Deployment Pipelines as a Competitive Advantage

    Deployment pipelines allow us to push to production at ever increasing volume. Paths to production looks at how some of software's most well known shops continuous deliver code.

  • Java, The Platform

    Mobile, Micro, Modular: The platform continues to evolve and change. Discover how the platform continues to drive us forward.

  • Security for Engineers

    How to build secure, yet usable, systems from the engineer's perspective.

  • Modern Data Engineering

    The innovations necessary to build towards a fully automated decentralized data warehouse.

  • Machine Learning for the Software Engineer

    AI and machine learning are more approachable than ever. Discover how ML, deep learning, and other modern approaches are being used in practice by Software Engineers.

  • Inclusion & Diversity in Tech

    The road map to an inclusive and diverse tech organization. *Diversity & Inclusion defined as the inclusion of all individuals in an within tech, regardless of gender, religion, ethnicity, race, age, sexual orientation, and physical or mental fitness.

  • Tuesday, 17 November

  • Architectures You've Always Wondered About

    How do they do it? In QCon's marquee Architectures track, we learn what it takes to operate at large scale from well-known names in our industry. You will take away hard-earned architectural lessons on scalability, reliability, throughput, and performance.

  • Architecting for Confidence: Building Resilient Systems

    Your system will fail. Build systems with the confidence to know when they do and you won’t.

  • Remotely Productive: Remote Teams & Software

    More and more companies are moving to remote work. How do you build, work on, and lead teams remotely?

  • Operating Microservices

    Building and operating distributed systems is hard, and microservices are no different. Learn strategies for not just building a service but operating them at scale.

  • Distributed Systems for Developers

    Computer science in practice. An applied track that fuses together the human side of computer science with the technical choices that are made along the way

  • The Future of APIs

    Web-based API continue to evolve. The track provides the what, how, and why of future APIs, including GraphQL, Backend for Frontend, gRPC, & ReST

  • Wednesday, 18 November

  • Resurgence of Functional Programming

    What was once a paradigm shift in how we thought of programming languages is now main stream in nearly all modern languages. Hear how software shops are infusing concepts like pure functions and immutablity into their architectures and design choices.

  • Social Responsibility: Implications of Building Modern Software

    Software has an ever increasing impact on individuals and society. Understanding these implications helps build software that works for all users

  • Non-Technical Skills for Technical Folks

    To be an effective engineer, requires more than great coding skills. Learn the subtle arts of the tech lead, including empathy, communication, and organization.

  • Clientside: From WASM to Browser Applications

    Dive into some of the technologies that can be leveraged to ultimately deliver a more impactful interaction between the user and client.

  • Languages of Infra

    More than just Infrastructure as a Service, today we have libraries, languages, and platforms that help us define our infra. Languages of Infra explore languages and libraries being used today to build modern cloud native architectures.

  • Mechanical Sympathy: The Software/Hardware Divide

    Understanding the Hardware Makes You a Better Developer