How We Optimised Our Application to serve 100 requests/sec with response time of 10ms

Photo by Cesar Carlevarino Aragon on Unsplash

Not a long time back, I was working on a side project. I was trying to make URL shortner service with the aim to make it serve 100 requests per second, with each request taking 15ms or less. This blog outlines the steps I took to optimise my system and achieve my goals

Before I start, I want to thank my mentors, Abhinav Dhasmana, Atul R, and Kakul Gupta, for their guidance. Without their mentoring I would not have been able to convert my goals to reality

Table of contents:

  1. Introduction — The system
  2. The initial System and hunt for optimisation points
  3. Optimisation 1 — Efficient writes: DB optimisation
  4. Optimisation 2 — Efficient reads: Caching
  5. Optimisation 3 — Multiple instances

Introduction — The system

The project which we built was a URL shortner service, similar to The goal of the system is to provide user, the ability to shorten a long URL. Making it easy to share across the internet.

The tech stack used are as follows:

In this blog, Im going to restrict myself by talking only about the performance optimisation. If you are interested in learning about the system, and various design decision that we took, head over to Abhinav’s article. This blog, goes in depth about system design of a URL shortner service.

The initial System and hunt for optimisation points

The flow of the initial system is as follows:

Flow to create a short URL, given a long URL
Flow to fetch a long URL. Given a short URL

With this implementation, we performed a load testing using JMeter. We got response time of 40ms. Following is the screenshot for reference:

Performance without any optimisation: 40ms

To find the points of optimisation in our system, we divided the application in 3 parts. These are:

  1. Database optimisation for efficient read/write operations
  2. Since our application has more read operations than write. Use cache
  3. Utilising all cores of our hardware

I will now discuss, how we optimised these points individually

Optimisation 1 — Efficient writes: DB optimization

This optimisation affects the read/write of the URL to the database. Since, our application depends heavily on the read/write speed of the database, we set up database pooling so that we have a pool of open database connections. This reduces the time required to create a connection to database

We set up a pool of connection range between 5 and 20. With idle timeout set as 10s

Optimisation 2 — Efficient reads: Caching

If we trace the happy path of user testing, we can observe that a user will write a short url once. Whereas, the read for the same URL will be multiple times by multiple users. To reduce the time of reading database, we introduced cache.

The cache that we decided to go forward was Redis. After incorporating caching, our flow became as follows:

Modified flow with caching

Optimisation 3 — Multiple instances

NodeJs is single threaded. It cannot utilise all the cores of our system. To achieve the utilisation of multiple cores, we used pm2. This enabled our application to handle more input connections. This pertains to the 100 req/sec part


After incorporating all the above mentioned optimisation, we achieved our target. The final application gave us response time of 5ms. Refer to following screenshot for reference:

Performance after incorporating all optimisations

The complete code can be found here

If you liked this post, please clap for this post. Your claps motivates me to keep writing articles




Full stack developer @Cisco, Ex-@McKinsey | Bibliophile | Coder by heart | Opinions are mine

Love podcasts or audiobooks? Learn on the go with our new app.

Recommended from Medium

How to Start Using Django in 4 mins

Nova 2.0: Re-architecting the Analytics Engine behind Amplitude

Building a Secured Flutter Application

The Essence of Algorithm: Greedy algorithms

ATT&CK 2021 Roadmap

HTML and CSS simplified

PostgresSQL tutorial -1

How many R’s are there in Cloud Migration?

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Siddharth Lakhara

Siddharth Lakhara

Full stack developer @Cisco, Ex-@McKinsey | Bibliophile | Coder by heart | Opinions are mine

More from Medium

MongoDB Query Performance Tip

What is Redis?

Testing a web server : Part 1

Creating a HTTP Server with NodeJS and logging requests with promised fs