Performance Testing Interview Questions: JMeter, k6 & LoadRunner (2026)

Answer: Performance testing evaluates how a system behaves under workload — measuring speed, responsiveness, stability, and scalability. It's critical for preventing slowdowns, crashes, and revenue loss during peak traffic.

Answer: Latency is the delay before data transfer begins (network + processing overhead). Response time is the total time from request to complete response (latency + data transfer).

Practice performance testing concepts with our AI Mock Interview.

Answer: An open-source performance testing tool for load testing web applications, APIs, databases, and more. Supports protocol-level testing (HTTP, HTTPS, JDBC, FTP, JMS). See the official Apache JMeter docs.

• Thread Group: Simulates users; configure threads (users), ramp-up, and loop count
• Sampler: Sends requests (HTTP Request, JDBC Request, etc.)
• Listener: Captures and displays results (View Results Tree, Aggregate Report, Graphs)
• Timer: Adds delays between requests (Constant Timer, Gaussian Random Timer)
• Assertion: Validates responses (Response Assertion, Duration Assertion)
• Configuration Element: Sets defaults, variables (CSV Data Set Config, HTTP Cookie Manager)
• Pre/Post Processors: Modify requests/responses

Answer: Use CSV Data Set Config to read data from CSV files — user credentials, product IDs, search queries. This enables data-driven performance testing with realistic data.

• Basic Auth: HTTP Authorization Manager
• JWT/Bearer Token: JSON Extractor + BeanShell/JSR223 PostProcessor to extract and set token
• Cookie-based: HTTP Cookie Manager handles cookies automatically

• Response Assertion: Match pattern in response text
• Duration Assertion: Verify response time threshold
• Size Assertion: Check response size limits
• HTML Assertion: Validate HTML syntax

1. SetUp Thread Group — Initialization before tests (login, setup data)
2. Regular Thread Groups — Main load test
3. TearDown Thread Group — Cleanup after tests (logout, delete data)

Get more practice questions from our Selenium & automation interview questions.

• 3 Basic Graphs — Response Times Over Time, Active Threads Over Time
• Custom Thread Groups — Ultimate Thread Group, Free-Form Arrivals
• PerfMon — Server resource monitoring (CPU, memory, disk I/O)

jmeter -n -t test_plan.jmx -l results.jtl -e -o reports/

• -n: Non-GUI mode
• -t: Test plan file
• -l: Results log
• -e + -o: Generate HTML dashboard

Answer: Master-slave architecture where one master controls multiple slave machines to generate high load. Configure remote_hosts in jmeter.properties, start slaves, then run from master.

Answer: k6 is a modern, developer-friendly performance testing tool using JavaScript. Unlike JMeter (GUI-based), k6 is code-first, lightweight, and designed for CI/CD integration.

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

export let options = {
  vus: 10,        // virtual users
  duration: '30s', // test duration
  thresholds: {
    http_req_duration: ['p(95)<500'], // 95% requests under 500ms
    http_req_failed: ['rate<0.01'],   // <1% failure rate
  }
};

export default function () {
  let res = http.get('https://test-api.com/users');
  check(res, {
    'status is 200': (r) => r.status === 200,
    'response time < 300ms': (r) => r.timings.duration < 300,
  });
  sleep(1);
}

Answer: Pass/fail criteria for performance tests. Automatically fail the test if conditions aren't met:

thresholds: {
  http_req_duration: ['p(95)<500', 'avg<300'],
  http_req_failed: ['rate<0.01'],
  'checks{type:critical}': ['rate>0.99']
}

Answer: k6 is CI-native:

• GitHub Actions: Use grafana/k6-action
• GitLab CI: Run k6 run script.js
• Docker: docker run -i grafana/k6 run - < script.js

Answer: Managed platform for running k6 tests at scale, storing results, and visualizing performance trends over time.

Answer: Enterprise-level performance testing tool supporting 50+ protocols (HTTP, SAP, Oracle, Citrix, etc.). Used by large organizations for comprehensive testing.

• VuGen (Virtual User Generator) — Creates scripts
• Controller — Designs and runs scenarios
• Load Generator — Generates virtual user load
• Analysis — Analyzes results and generates reports

• vuser_init — Login, initialize (runs once per Vuser)
• Action — Main business logic (repeats based on iterations)
• vuser_end — Logout, cleanup (runs once per Vuser)

Answer: Dynamic value extraction using web_reg_save_param() or auto-correlation. Similar to JMeter's correlation concept.

Answer: A point where multiple virtual users synchronize to perform an action simultaneously — used for stress testing specific features.

1. Identify critical business workflows
2. Define expected load (concurrent users, TPS)
3. Set performance targets (response time < 2s, error rate < 1%)
4. Determine test environment (staging/production mirror)
5. Plan monitoring (APM, server metrics, logs)

Answer: A reference point establishing normal system performance under defined conditions. Compare future tests against the baseline to detect regressions.

1. Database: Slow queries, missing indexes, connection pool exhaustion
2. Network: Latency, bandwidth limits, DNS resolution
3. Application: Memory leaks, inefficient algorithms, thread contention
4. Infrastructure: CPU saturation, disk I/O limits, insufficient RAM

Answer: Use business data: average daily users × peak factor ÷ average session duration = concurrent users. For example: 100,000 daily users × 3x peak × 15 min average session ÷ 24 hours ≈ 3,125 concurrent users.

Browse QA jobs that require performance testing skills.