Skip to content

General Load Testing Report

This document explains how our application behaves when many people use it at the same time. It avoids technical jargon and focuses on what matters: the user experience and how to make it better.

The Big Picture: How many users can we handle?

We tested our system by simulating different numbers of people using the app simultaneously. Here is the simple truth of what happens:

Number of Active Users User Experience What the User Sees Our Verdict
Up to 20 users Excellent Screens load instantly (under 0.4 seconds). Perfect. No action needed.
50 users Acceptable Screens take about 1 second to load. It is noticeable but acceptable. Good. We are at the limit of our current setup.
100 users Frustrating Screens take about 2.5 seconds to load. Users will feel the app is slow. Bad. We need to optimize the system.
200 users Broken The app stops responding. Users see loading spinners that never finish or error messages. Failure. The system crashes and must be restarted.

Why does the system slow down or break?

Imagine a supermarket with only one cashier open:

  1. The "Single Cashier" Bottleneck: Our server currently runs as a single process. It is like having only one cashier. If 20 people are in the store, they get checked out quickly. If 100 people arrive at once, a long line forms, and everyone waits.

  2. The Database Gets Overwhelmed: When 200 users hit the app, the server runs out of "connections" to the database. It is like the cashier's computer freezing because too many transactions are happening at once. The system gets stuck and needs a manual restart to work again.

  3. Logging In is Heavy Work: Logging in requires high-security password checking. This takes a lot of computer brainpower. When many people try to log in at the same time, it slows down all other simple tasks (like viewing factories or tasks).

What about uploading files and downloading data?

We also tested what happens when people upload large files (like 12 MB images) or load large lists of data.

  • The Good News: If only a few people (1 to 5 users) are doing this, the system handles it perfectly and very quickly.
  • The Catch: If 50 people try to upload huge files at the exact same time, it will make the "Single Cashier" queue even worse.

How do we fix this? (Our Action Plan)

To make the app ready for hundreds of users, we need to do three simple things:

  1. Open More Checkout Lanes (Add Server Workers): We can easily configure our server to run 4 "workers" instead of 1. This is like opening 4 cashier lanes instead of 1. It will instantly multiply our capacity.

  2. Increase Database Capacity: We need to adjust our database settings so it can handle more simultaneous connections without freezing.

  3. Test Again: Once we open more lanes and increase database capacity, we will run the tests again to prove that 100+ users can browse the app with zero lag.