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:36:55 UTC

cvs commit: jakarta-jmeter/xdocs/usermanual boss.xml

woolfel     2004/01/12 20:36:55

  Modified:    xdocs/usermanual boss.xml
  Log:
  updated the section numbers.
  
  peter lin
  
  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       +17 -17    jakarta-jmeter/xdocs/usermanual/boss.xml
  
  Index: boss.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-jmeter/xdocs/usermanual/boss.xml,v
  retrieving revision 1.7
  retrieving revision 1.8
  diff -u -r1.7 -r1.8
  --- boss.xml	12 Jun 2003 13:39:42 -0000	1.7
  +++ boss.xml	13 Jan 2004 04:36:55 -0000	1.8
  @@ -8,14 +8,14 @@
   
   <body>
   
  -<section name="12. Help! My boss wants me to load test our web app!" anchor="boss">
  +<section name="13. 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="12.1 Questions to ask">
  +<subsection name="13.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 ?
  @@ -27,13 +27,13 @@
   (cookies, session-rewriting, or some other method) ?
   </p>
   </subsection>
  -<subsection name="12.2 Resources">
  +<subsection name="13.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="12.2.1 Network">
  +	<subsection name="13.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)
  @@ -43,7 +43,7 @@
   	hardware ?
   	</p>
   	</subsection>
  -	<subsection name="12.2.2 Application">
  +	<subsection name="13.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>
  @@ -60,7 +60,7 @@
   	</p>
   	</subsection>
   </subsection>
  -<subsection name="12.3 What platform should I use to run the benchmarks/load-tests ?">
  +<subsection name="13.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.
  @@ -91,20 +91,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="12.4 Tools">
  +<subsection name="13.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="12.4.1 ping">
  +	<subsection name="13.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="12.4.2 nslookup/dig">
  +	<subsection name="13.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
  @@ -112,7 +112,7 @@
   	the unique address (dotted quad) of your target site.
   	</p>
   	</subsection>
  -	<subsection name="12.4.3 traceroute">
  +	<subsection name="13.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
  @@ -123,7 +123,7 @@
   	</p>
   	</subsection>
   </subsection>
  -<subsection name="12.5 What other products are there ?">
  +<subsection name="13.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
  @@ -131,7 +131,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="12.5.1 Apache 'ab' tool">
  +	<subsection name="13.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
  @@ -139,7 +139,7 @@
   	performance reporting.
   	</p>
   	</subsection>
  -	<subsection name="12.5.2 HttpUnit">
  +	<subsection name="13.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
  @@ -147,14 +147,14 @@
   	conjunction with <b>JUnit</b>.
   	</p>
   	</subsection>
  -	<subsection name="12.5.3 Microsoft WAS">
  +	<subsection name="13.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="12.5.4 JMeter">
  +	<subsection name="13.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
  @@ -163,7 +163,7 @@
   	</p>
   	</subsection>
   </subsection>
  -<subsection name="12.6 Why Java ?">
  +<subsection name="13.6 Why Java ?">
   <p>Why not Perl or C ?
   </p>
   <p>Well, Perl might be a very good choice except that the Benchmark package
  
  
  

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