You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jmeter-dev@jakarta.apache.org by wo...@apache.org on 2004/10/08 06:33:44 UTC
cvs commit: jakarta-jmeter/xdocs/usermanual listeners.xml glossary.xml remote-test.xml index.xml boss.xml best-practices.xml
woolfel 2004/10/07 21:33:44
Modified: xdocs/usermanual glossary.xml remote-test.xml index.xml
boss.xml best-practices.xml
Added: xdocs/usermanual listeners.xml
Log:
added a section on listeners and a short explanation of how to save
any listener using the new save as image feature.
peter
Revision Changes Path
1.9 +3 -3 jakarta-jmeter/xdocs/usermanual/glossary.xml
Index: glossary.xml
===================================================================
RCS file: /home/cvs/jakarta-jmeter/xdocs/usermanual/glossary.xml,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- glossary.xml 23 Mar 2004 17:00:58 -0000 1.8
+++ glossary.xml 8 Oct 2004 04:33:44 -0000 1.9
@@ -23,7 +23,7 @@
<body>
-<section name="17. Glossary" anchor="glossary">
+<section name="18. Glossary" anchor="glossary">
</section>
</body>
1.18 +4 -4 jakarta-jmeter/xdocs/usermanual/remote-test.xml
Index: remote-test.xml
===================================================================
RCS file: /home/cvs/jakarta-jmeter/xdocs/usermanual/remote-test.xml,v
retrieving revision 1.17
retrieving revision 1.18
diff -u -r1.17 -r1.18
--- remote-test.xml 12 Jun 2004 17:11:46 -0000 1.17
+++ remote-test.xml 8 Oct 2004 04:33:44 -0000 1.18
@@ -23,7 +23,7 @@
<body>
-<section name="12. Remote Testing">
+<section name="13. Remote Testing">
<p>In the event that your JMeter client machine is unable, performance-wise, to simulate
enough users to stress your server, an option exists to control multiple, remote JMeter
@@ -67,7 +67,7 @@
normal JMeter start and stop menu items.</p>
<p><img src="../images/screenshots/remote/run-menu00.gif" width="232" height="156"></img>
<br>Figure 1 - Run Menu</br></p>
-<subsection name="12.1 Doing it Manually" anchor="detail_instructions">
+<subsection name="13.1 Doing it Manually" anchor="detail_instructions">
<p>In some cases, the jmeter-server script may not work for you (if you are using an OS platform not anticipated by the JMeter developers). Here is how to start the JMeter servers (step 1 above) with a more manual process:</p>
<p><b>Step 1a: Start the RMI Registry</b></p>
<p>JMeter uses Remote Method Invocation (RMI) as the remote communication mechanism. Therefore, you need
1.35 +21 -19 jakarta-jmeter/xdocs/usermanual/index.xml
Index: index.xml
===================================================================
RCS file: /home/cvs/jakarta-jmeter/xdocs/usermanual/index.xml,v
retrieving revision 1.34
retrieving revision 1.35
diff -u -r1.34 -r1.35
--- index.xml 17 Aug 2004 21:44:03 -0000 1.34
+++ index.xml 8 Oct 2004 04:33:44 -0000 1.35
@@ -40,12 +40,13 @@
<li><a href="#build-ldapext-test-plan">+</a>...<a href="build-ldapext-test-plan.html">9b. Building an Extended LDAP Test Plan</a></li>
<li><a href="#build-ws-test-plan">+</a>...<a href="build-ws-test-plan.html">10. Building a Webservice Test Plan</a></li>
<li><a href="#build-monitor-test-plan">+</a>...<a href="build-monitor-test-plan.html">11. Building a Monitor Test Plan</a></li>
- <li><a href="#remote-test">+</a>...<a href="remote-test.html">12. Remote Testing</a></li>
- <li><a href="#best-practices">+</a>...<a href="best-practices.html">13. Best Practices</a></li>
- <li><a href="#boss">+</a>...<a href="boss.html">14. Help! My boss wants me to load test our web app!</a></li>
- <li><a href="#component_reference">+</a>...<a href="component_reference.html">15. Component Reference</a></li>
- <li><a href="#functions">+</a>...<a href="functions.html">16. Functions</a></li>
- <li><a href="#glossary">+</a>...<a href="glossary.html">17. Glossary</a></li>
+ <li><a href="#listeners">+</a>...<a href="listeners.html">12. Listeners</a></li>
+ <li><a href="#remote-test">+</a>...<a href="remote-test.html">13. Remote Testing</a></li>
+ <li><a href="#best-practices">+</a>...<a href="best-practices.html">14. Best Practices</a></li>
+ <li><a href="#boss">+</a>...<a href="boss.html">15. Help! My boss wants me to load test our web app!</a></li>
+ <li><a href="#component_reference">+</a>...<a href="component_reference.html">16. Component Reference</a></li>
+ <li><a href="#functions">+</a>...<a href="functions.html">17. Functions</a></li>
+ <li><a href="#glossary">+</a>...<a href="glossary.html">18. Glossary</a></li>
</ul>
</subsection>
<subsection name="Detailed Section List">
@@ -154,19 +155,20 @@
</ul>
<li><a name="build-ws-test-plan"/><a href="build-ws-test-plan.html">10. Building a Webservice Test Plan</a></li>
<li><a name="build-monitor-test-plan"/><a href="build-monitor-test-plan.html">11. Building a Monitor Test Plan</a></li>
- <li><a name="remote-test"/><a href="remote-test.html">12. Remote Testing</a></li>
- <li><a name="best-practices"/><a href="best-practices.html">13. Best Practices</a></li>
- <ul>
- <li><a href="best-practices.html#limit_threads">13.1 [ALL] Limit the Number of Threads</a></li>
- <li><a href="best-practices.html#put_cookie_manager">13.2 [HTTP] Where to Put the Cookie Manager</a></li>
- <li><a href="best-practices.html#put_auth_manager">13.3 [HTTP] Where to Put the Authorization Manager</a></li>
- <li><a href="best-practices.html#proxy_server">13.4 Using the Proxy Server to record test scripts</a></li>
+ <li><a name="listeners"/><a href="listeners.html">12. Listeners</a></li>
+ <li><a name="remote-test"/><a href="remote-test.html">13. Remote Testing</a></li>
+ <li><a name="best-practices"/><a href="best-practices.html">14. Best Practices</a></li>
+ <ul>
+ <li><a href="best-practices.html#limit_threads">14.1 [ALL] Limit the Number of Threads</a></li>
+ <li><a href="best-practices.html#put_cookie_manager">14.2 [HTTP] Where to Put the Cookie Manager</a></li>
+ <li><a href="best-practices.html#put_auth_manager">14.3 [HTTP] Where to Put the Authorization Manager</a></li>
+ <li><a href="best-practices.html#proxy_server">14.4 Using the Proxy Server to record test scripts</a></li>
</ul>
- <li><a name="boss"/><a href="boss.html">14. Help! My boss wants me to load test our web app!</a></li>
+ <li><a name="boss"/><a href="boss.html">15. Help! My boss wants me to load test our web app!</a></li>
- <li><a name="component_reference"/><a href="component_reference.html">15. Component Reference</a></li>
- <li><a name="functions"/><a href="functions.html">16. Functions</a></li>
- <li><a name="glossary"/><a href="glossary.html">17. Glossary</a></li>
+ <li><a name="component_reference"/><a href="component_reference.html">16. Component Reference</a></li>
+ <li><a name="functions"/><a href="functions.html">17. Functions</a></li>
+ <li><a name="glossary"/><a href="glossary.html">18. Glossary</a></li>
</ul>
</subsection>
1.12 +18 -18 jakarta-jmeter/xdocs/usermanual/boss.xml
Index: boss.xml
===================================================================
RCS file: /home/cvs/jakarta-jmeter/xdocs/usermanual/boss.xml,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -r1.11 -r1.12
--- boss.xml 23 Mar 2004 17:00:58 -0000 1.11
+++ boss.xml 8 Oct 2004 04:33:44 -0000 1.12
@@ -25,14 +25,14 @@
<body>
-<section name="14. Help! My boss wants me to load test our web app!" anchor="boss">
+<section name="15. Help! My boss wants me to load test our web app!" anchor="boss">
<p>This is a fairly open-ended proposition. There are a number of questions to
be asked first, and additionally a number of resources that will be needed. You
will need some hardware to run the benchmarks/load-tests from. A number of
tools will prove useful. There are a number of products to consider. And finally,
why is Java a good choice to implement a load-testing/Benchmarking product.
</p>
-<subsection name="14.1 Questions to ask">
+<subsection name="15.1 Questions to ask">
<p>What is our anticipated average number of users (normal load) ?
</p>
<p>What is our anticipated peak number of users ?
@@ -44,13 +44,13 @@
(cookies, session-rewriting, or some other method) ?
</p>
</subsection>
-<subsection name="14.2 Resources">
+<subsection name="15.2 Resources">
<p>The following resources will prove very helpful. Bear in mind that if you
cannot locate these resources, <b>you</b> will become these resources. As you
already have your work cut out for you, it is worth knowing who the following
people are, so that you can ask them for help if you need it.
</p>
- <subsection name="14.2.1 Network">
+ <subsection name="15.2.1 Network">
<p>Who knows our network topology ? If you run into any firewall or
proxy issues, this will become very important. As well, a private
testing network (which will therefore have very low network latency)
@@ -60,7 +60,7 @@
hardware ?
</p>
</subsection>
- <subsection name="14.2.2 Application">
+ <subsection name="15.2.2 Application">
<p>Who knows how our application functions ? The normal sequence is
<ul>
<li>test (low-volume - can we benchmark our application?)</li>
@@ -77,7 +77,7 @@
</p>
</subsection>
</subsection>
-<subsection name="14.3 What platform should I use to run the benchmarks/load-tests ?">
+<subsection name="15.3 What platform should I use to run the benchmarks/load-tests ?">
<p>This should be a widely-used piece of hardware, with a standard
(i.e. vanilla) software installation. Remember, if you publish your results,
the first thing your clients will do is hire a graduate student to verify them.
@@ -108,20 +108,20 @@
The batch log file can then be loaded into JMeter on a workstation for analysis, or you can
use CSV output and import the data into a spreadsheet.</p>
</subsection>
-<subsection name="14.4 Tools">
+<subsection name="15.4 Tools">
<p>The following tools will all prove useful. It is definitely worthwhile to
become familiar with them. This should include trying them out, and reading the
appropriate documentation (man-pages, info-files, application --help messages,
and any supplied documentation).
</p>
- <subsection name="14.4.1 ping">
+ <subsection name="15.4.1 ping">
<p>
This can be used to establish whether or not you can reach your
target site. Options can be specified so that 'ping' provides the
same type of route reporting as 'traceroute'.
</p>
</subsection>
- <subsection name="14.4.2 nslookup/dig">
+ <subsection name="15.4.2 nslookup/dig">
<p>
While the <u>user</u> will normally use a human-readable internet
address, <u>you</u> may wish to avoid the overhead of DNS lookups when
@@ -129,7 +129,7 @@
the unique address (dotted quad) of your target site.
</p>
</subsection>
- <subsection name="14.4.3 traceroute">
+ <subsection name="15.4.3 traceroute">
<p>
If you cannot "ping" your target site, this may be used to determine
the problem (possibly a firewall or a proxy). It can also be used
@@ -140,7 +140,7 @@
</p>
</subsection>
</subsection>
-<subsection name="14.5 What other products are there ?">
+<subsection name="15.5 What other products are there ?">
<p>There are a number of commercial products, which generally have fairly
hefty pricetags. If you can justify it, these are probably the way to go.
If, however, these products do not do exactly what you want, or you are on a
@@ -148,7 +148,7 @@
start by trying the Apache <b>ab</b> tool, as it may very well do the job
if your requirements are not particularly complicated.
</p>
- <subsection name="14.5.1 Apache 'ab' tool">
+ <subsection name="15.5.1 Apache 'ab' tool">
<p>
You should definitely start with this one. It handles HTTP 'get' requests
very well, and can be made to handle HTTP 'post' requests with a little
@@ -156,7 +156,7 @@
performance reporting.
</p>
</subsection>
- <subsection name="14.5.2 HttpUnit">
+ <subsection name="15.5.2 HttpUnit">
<p>
This is worth a look. It is a library (and therefore of more interest to
developers) that can be used to perform HTTP tests/benchmarks. It is
@@ -164,14 +164,14 @@
conjunction with <b>JUnit</b>.
</p>
</subsection>
- <subsection name="14.5.3 Microsoft WAS">
+ <subsection name="15.5.3 Microsoft WAS">
<p>
This is definitely worth a look. It has an excellent user interface
but it may not do exactly what you want. If this is the case, be aware
that the functionality of this product is not likely to change.
</p>
</subsection>
- <subsection name="14.5.4 JMeter">
+ <subsection name="15.5.4 JMeter">
<p>
If you have non-standard requirements, then this solution offers an
open-source community to provide them (of course, if you are reading
@@ -180,7 +180,7 @@
</p>
</subsection>
</subsection>
-<subsection name="14.6 Why Java ?">
+<subsection name="15.6 Why Java ?">
<p>Why not Perl or C ?
</p>
<p>Well, Perl might be a very good choice except that the Benchmark package
1.11 +7 -7 jakarta-jmeter/xdocs/usermanual/best-practices.xml
Index: best-practices.xml
===================================================================
RCS file: /home/cvs/jakarta-jmeter/xdocs/usermanual/best-practices.xml,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- best-practices.xml 23 Mar 2004 17:00:58 -0000 1.10
+++ best-practices.xml 8 Oct 2004 04:33:44 -0000 1.11
@@ -25,10 +25,10 @@
<body>
-<section name="13. Best Practices" anchor="best_practices">
+<section name="14. Best Practices" anchor="best_practices">
</section>
-<section name="13.1 Limit the Number of Threads" anchor="limit_threads">
+<section name="14.1 Limit the Number of Threads" anchor="limit_threads">
<p>Your hardware's capabilities will limit the number of threads you can effectively
run with JMeter. It will also depend on how fast your server is (a faster server
gives makes JMeter work harder since it returns request quicker). The more
@@ -38,17 +38,17 @@
<a href="remote-test.html">running JMeter remotely</a> across multiple machines.</p>
</section>
-<section name="13.2 Where to Put the Cookie Manager" anchor="put_cookie_manager">
+<section name="14.2 Where to Put the Cookie Manager" anchor="put_cookie_manager">
<p>See <a href="build-web-test-plan.html#adding_cookie_support">Building a Web Test</a>
for information.</p>
</section>
-<section name="13.3 Where to Put the Authorization Manager" anchor="put_auth_manager">
+<section name="14.3 Where to Put the Authorization Manager" anchor="put_auth_manager">
<p>See <a href="build-adv-web-test-plan.html#header_manager">Building an Advanced
Web Test</a> for information.</p>
</section>
-<section name="13.4 Using the Proxy Server" anchor="proxy_server">
+<section name="14.4 Using the Proxy Server" anchor="proxy_server">
<p>Refer to <complink name="HTTP Proxy Server"/> for details on setting up the proxy
server. The most important thing to do is filter out all requests you aren't
interested in. For instance, there's no point in recording image requests (JMeter can
1.1 jakarta-jmeter/xdocs/usermanual/listeners.xml
Index: listeners.xml
===================================================================
<?xml version="1.0"?>
<!--
$Header: /home/cvs/jakarta-jmeter/xdocs/usermanual/listeners.xml,v 1.1 2004/10/08 04:33:44 woolfel Exp $
Copyright 2001-2004 The Apache Software Foundation
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
-->
<document prev="build-monitor-test-plan.html" next="remote-test.html" date="$Date: 2004/10/08 04:33:44 $">
<properties>
<title>User's Manual: Listeners</title>
</properties>
<body>
<section name="12. Introduction to listeners" anchor="intro">
<p>For those new to JMeter, a listener is a component that shows the results of the
samples. The results can be shown in a tree, tables, graphs or simply written to a log
file. To view the contents of a response from any given sampler, add either view
results tree or in table to a test plan. To view the response time graphically, add
graph results, spline results or distribution graph. For detailed explanation, of
each listener, please go to the components page.</p>
</section>
<section name="12.1 Screen captures" anchor="screencap">
<p>JMeter is capable of saving any listener as a PNG file. To do so, select the
listener in the left panel. Click edit -> Save As Image. A file dialog will
appear. Enter the desired name and save the listener.
</p>
<figure image="save_image.png">Figure 1 - Edit -> Save As Image</figure>
</section>
</body>
</document>
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-dev-help@jakarta.apache.org