svn commit: r946697 - /jakarta/jmeter/trunk/xdocs/usermanual/remote-test.xml

[se...@apache.org]

Author: sebb
Date: Thu May 20 16:37:45 2010
New Revision: 946697

URL: http://svn.apache.org/viewvc?rev=946697&view=rev
Log:
More detail of how client-server works

Modified:
    jakarta/jmeter/trunk/xdocs/usermanual/remote-test.xml

Modified: jakarta/jmeter/trunk/xdocs/usermanual/remote-test.xml
URL: http://svn.apache.org/viewvc/jakarta/jmeter/trunk/xdocs/usermanual/remote-test.xml?rev=946697&r1=946696&r2=946697&view=diff
==============================================================================
--- jakarta/jmeter/trunk/xdocs/usermanual/remote-test.xml (original)
+++ jakarta/jmeter/trunk/xdocs/usermanual/remote-test.xml Thu May 20 16:37:45 2010
@@ -39,10 +39,15 @@ all the data from them.  This offers the
 
 
 <ul>
-<li>Saving of test samples to a local machine </li>
+<li>Saving of test samples to the local machine </li>
 <li>Managment of multiple JMeterEngines from a single machine </li>
+<li>No need to copy the test plan to each server - the client sends it to all the servers</li>
 </ul>
 </p>
+<note>
+Note: The same test plan is run by all the servers.
+JMeter does not distribute the load between servers, each runs the full test plan.
+</note>
 <p>
 However, remote mode does use more resources than running the same number of non-GUI tests independently.
 If many server instances are used, the client JMeter can become overloaded, as can the client network connection.
@@ -57,6 +62,22 @@ results without impacting the performanc
 itself.
 </p>
 
+<p><b>Step 0: Configure the server nodes</b></p>
+<p>
+Make sure that all the servers are running exactly the same version of JMeter.
+As far as possible, use the same version of Java on all systems.
+Using different versions of Java may work - but is best avoided.
+</p>
+<p>
+If the test uses any data files, note that these are not sent across by the client so
+make sure that these are available in the appropriate directory.
+If necessary you can define different values for properties by editting the user.properties or system.properties
+files on each server. These properties will be picked up when the server is started and may be
+used in the test plan to affect its behaviour (e.g. connecting to a different remote server).
+Alternatively use different content in any datafiles used by the test 
+(e.g. if each server must use unique ids, divide these between the data files)
+</p>
+
 <p><b>Step 1: Start the servers </b></p>
 <p>To run JMeter in remote node, start the JMeter server component on all machines you wish to run on by running the <b>JMETER_HOME/bin/jmeter-server</b> (unix) or <b>JMETER_HOME/bin/jmeter-server.bat</b> (windows) script.</p>
 <p>Note that there can only be one JMeter server on each node unless different RMI ports are used.</p>



---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@jakarta.apache.org
For additional commands, e-mail: notifications-help@jakarta.apache.org