LOAD TEST LAB Resources
Menu
← Back to Load Test Lab

Network architecture

Measure the application instead of an unrelated tunnel.

Network placement affects every load-test result. With the Agent installed next to the customer’s JMeter load generator, generated traffic follows the customer-selected route directly to the system under test.

By Load Test Lab product team Reviewed by Kedros, a.s. Updated Product version 1.0.0

Agent

Configure the Load Test Lab Agent for the active team.

Team Agent

Customer-controlled load generator connection

Configured

Team Agent

Agent ID agent-demo-team
Topic loadtestlab/demo-team/agent
Load tool home /opt/load-tool
Work directory /var/lib/loadtestlab
JWT or certificate Valid · 74 days

Preview of the current Load Test Lab interface. Example data only.

01

Place the generator near the target

Select a host that already has representative access to the test environment. Internal applications can remain reachable through the customer network without exposing the target to a managed load cloud.

02

Separate coordination from generated traffic

Load Test Lab sends commands and receives status, result files, and logs. The high-volume JMeter traffic itself travels between the customer load generator and the tested application.

03

Validate the complete network path

Before interpreting latency or throughput, confirm load-generator capacity, target connectivity, proxy configuration, and any customer VPN that is intentionally part of the chosen route.

Put Load Test Lab into practice

Prove the value with a real test.

Start with the scripts and load generator your team already uses.