Skip to main content

Parametri di Input

Formule

  • Concurrent Users = (Peak Users × Session Duration) / 3600
  • RPS = (Concurrent Users × Pages/Session) / Session Duration (s)
  • Bandwidth = RPS × Avg Page Size × 8
  • Thread Pool = Concurrent Users × 1.5
  • Connection Pool = Concurrent Users × 1.2

Risultati

Utenti Concorrenti834
RPS (Richieste/sec)23
Bandwidth Richiesta92.0 Mbps
Thread Pool Size1251
Connection Pool Size1001
Dim. pagina assunta500 KB

Config Snippet

import http from 'k6/http';
import { sleep } from 'k6';

export const options = {
  vus: 834,
  duration: '5m',
  thresholds: {
    http_req_duration: ['p(95)<300'],
    http_req_failed: ['rate<0.01'],
  },
};

export default function () {
  http.get('https://your-target-url.com/');
  sleep(2176);
}

Come utilizzare Load Test Calculator

Insert traffic expected parameters

Indicate daily expected users, hourly peak percentage, average session duration, pages per session, and average response time.

Read calculated parameters

The tool applies formulas (visible in the Formulas section) to derive competing users, RPS, bandwidth required, thread pool, and connection pool size.

Generate and copy K6/JMeter config

Choose the format (k6 or JMeter), copy the generated snippet and replace the target URL before running the load test.

Suggerimenti

  • Start with a conservative estimate of user traffic during peak hours (15-25% typical for B2C traffic) and refine after observing actual log data.
  • If your backend has an already sized connection pool, compare the suggested value with the real one to understand if you risk saturation under load.
  • Use K6 for testable and integratable scripts in CI/CD, JMeter if you prefer a graphical interface or existing scenarios in that format.

Domande frequenti

How are concurrent user numbers calculated?

Concurrent Users = (Peak Users x Session Duration in seconds) / 3600, where Peak Users is the daily users expected during peak hour (dailyUsers * peakHourPct%).

Where does the page size used for bandwidth calculation come from?

The tool uses a fixed reference value of 500 KB per page (visible in the result "Page size taken"): if your site has heavier or more complex pages, recalculate the bandwidth manually using the formula RPS x real size x 8.

What's the difference between thread pool size and connection pool size?

Thread Pool Size (Concurrent Users x 1.5) estimates the number of application threads needed to handle load with buffer; Connection Pool Size (Concurrent Users x 1.2) estimates database or downstream service connections with a more moderate buffer.

Is the K6/JMeter snippet ready for production?

The snippet is a starting point: it contains VU (virtual users) and calculated duration, but you need to replace the URL placeholder with your real target and adjust thresholds, headers, and testing scenarios to suit your specific needs.

Does the tool really run a load test on my site?

No, the tool only calculates sizing parameters and generates configuration; actual load test execution happens with k6 or JMeter installed locally or in CI, targeting your target URL.