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/01/13 05:35:23 UTC
cvs commit: jakarta-jmeter/xdocs/usermanual best-practices.xml
woolfel 2004/01/12 20:35:23
Modified: xdocs/usermanual best-practices.xml
Log:
updated the section numbers, now that I added build webservice
to the index.xml file
CVS: ----------------------------------------------------------------------
CVS: PR:
CVS: If this change addresses a PR in the problem report tracking
CVS: database, then enter the PR number(s) here.
CVS: Obtained from:
CVS: If this change has been taken from another system, such as NCSA,
CVS: then name the system in this line, otherwise delete it.
CVS: Submitted by:
CVS: If this code has been contributed to Apache by someone else; i.e.,
CVS: they sent us a patch or a new module, then include their name/email
CVS: address here. If this is your work then delete this line.
CVS: Reviewed by:
CVS: If we are doing pre-commit code reviews and someone else has
CVS: reviewed your changes, include their name(s) here.
CVS: If you have not had it reviewed then delete this line.
Revision Changes Path
1.8 +6 -6 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.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- best-practices.xml 17 Dec 2003 02:58:58 -0000 1.7
+++ best-practices.xml 13 Jan 2004 04:35:23 -0000 1.8
@@ -7,10 +7,10 @@
<body>
-<section name="11. Best Practices" anchor="best_practices">
+<section name="12. Best Practices" anchor="best_practices">
</section>
-<section name="11.1 Limit the Number of Threads" anchor="limit_threads">
+<section name="12.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
@@ -20,17 +20,17 @@
<a href="remote-test.html">running JMeter remotely</a> across multiple machines.</p>
</section>
-<section name="11.2 Where to Put the Cookie Manager" anchor="put_cookie_manager">
+<section name="12.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="11.3 Where to Put the Authorization Manager" anchor="put_auth_manager">
+<section name="12.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="11.4 Using the Proxy Server" anchor="proxy_server">
+<section name="12.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
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-dev-help@jakarta.apache.org