<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en-GB">
	<id>https://training-course-material.com/index.php?action=history&amp;feed=atom&amp;title=JMeter_Advanced_Slides</id>
	<title>JMeter Advanced Slides - Revision history</title>
	<link rel="self" type="application/atom+xml" href="https://training-course-material.com/index.php?action=history&amp;feed=atom&amp;title=JMeter_Advanced_Slides"/>
	<link rel="alternate" type="text/html" href="https://training-course-material.com/index.php?title=JMeter_Advanced_Slides&amp;action=history"/>
	<updated>2026-05-13T09:38:15Z</updated>
	<subtitle>Revision history for this page on the wiki</subtitle>
	<generator>MediaWiki 1.45.1</generator>
	<entry>
		<id>https://training-course-material.com/index.php?title=JMeter_Advanced_Slides&amp;diff=21113&amp;oldid=prev</id>
		<title>Łukasz Walec at 22:25, 8 August 2014</title>
		<link rel="alternate" type="text/html" href="https://training-course-material.com/index.php?title=JMeter_Advanced_Slides&amp;diff=21113&amp;oldid=prev"/>
		<updated>2014-08-08T22:25:06Z</updated>

		<summary type="html">&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;== Non-Test Elements ==&lt;br /&gt;
&lt;br /&gt;
A fast way to create Test Plan is to record every request made to the server. For this you will need to use HTTP(S) Test Script Recorder.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
This special-purpose element is only available in the WorkBench element.&lt;br /&gt;
&lt;br /&gt;
== Distributed Testing ==&lt;br /&gt;
&lt;br /&gt;
Distributed testing allows you to replicate tests across many machines, enabling you to start more threads and simulate heavy load on the server.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The features offered by this approach:&lt;br /&gt;
* Replicating the Test Plan from the master node to each controlled slave nodes&lt;br /&gt;
* Saving results to the local machine&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
JMeter does not distribute the load between servers. Each server will execute the same Test Plan.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The remote mode is more resource intensive than running the same number of non-GUI instances of JMeter independently.&lt;br /&gt;
&lt;br /&gt;
== Resource Monitoring ==&lt;br /&gt;
&lt;br /&gt;
Resource monitoring is a broad subject that covers analyzing system hardware usage, which includes CPU, memory, disk, and network.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
As you conduct testing, it is important to know how each of these resources are behaving under load to better understand if there are bottlenecks and address them accordingly.&lt;br /&gt;
&lt;br /&gt;
[[Category:JMeter]]&lt;/div&gt;</summary>
		<author><name>Łukasz Walec</name></author>
	</entry>
</feed>