Fleet and Distributed Runs
Running load from several machines with LoadLitmus Fleet - slaves over SSH, provisioning, ports, distributing test data and collecting failed responses.
Running load from several machines with LoadLitmus Fleet - slaves over SSH, provisioning, ports, distributing test data and collecting failed responses.
A tour of the LoadLitmus sidebar - what each page is for, when you open it, and which page of this track covers it.
Installing LoadLitmus, where its data folder lives, creating your first project, and the ports and access rules you need to know.
A practical guide to LoadLitmus, the on-premise web dashboard we use to run, store and report JMeter performance tests.
Reading a finished run in LoadLitmus - metrics, HTML reports, comparisons, exports and auto-analysis - plus live monitoring through InfluxDB.
The Runner page end to end - selecting a plan, setting load, parameters and data, watching the live log, stopping safely, and copying the run into CI.
What a JMeter .jmx file needs so LoadLitmus can drive its load, data and results - and which thread-group shapes turn features off.
A ready-made JMeter .jmx skeleton built for LoadLitmus - download it, fill in the placeholders, and start a project with the Load card, guards and portable paths already wired up.
What the LoadLitmus dashboard does, what it deliberately does not do, and when to use it instead of running JMeter by hand.