jmeter-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From fschumac...@apache.org
Subject svn commit: r1700292 - in /jmeter/trunk/xdocs/usermanual: get-started.xml realtime-results.xml remote-test.xml
Date Mon, 31 Aug 2015 18:27:36 GMT
Author: fschumacher
Date: Mon Aug 31 18:27:35 2015
New Revision: 1700292

URL: http://svn.apache.org/r1700292
Log:
Definition title is <dt> not <dh>.

Bugzilla Id: 53764

Modified:
    jmeter/trunk/xdocs/usermanual/get-started.xml
    jmeter/trunk/xdocs/usermanual/realtime-results.xml
    jmeter/trunk/xdocs/usermanual/remote-test.xml

Modified: jmeter/trunk/xdocs/usermanual/get-started.xml
URL: http://svn.apache.org/viewvc/jmeter/trunk/xdocs/usermanual/get-started.xml?rev=1700292&r1=1700291&r2=1700292&view=diff
==============================================================================
--- jmeter/trunk/xdocs/usermanual/get-started.xml (original)
+++ jmeter/trunk/xdocs/usermanual/get-started.xml Mon Aug 31 18:27:35 2015
@@ -291,11 +291,11 @@ options when <code>-jar</code> is used.
 the firewall/proxy server hostname and port number.  To do so, run the <code>jmeter[.bat]</code>
file
 from a command line with the following parameters:</p>
 <dl>
-<dh><code>-H</code></dh><dd>[proxy server hostname or ip address]</dd>
-<dh><code>-P</code></dh><dd>[proxy server port]</dd>
-<dh><code>-N</code></dh><dd>[nonproxy hosts] (e.g. <code>*.apache.org|localhost</code>)</dd>
-<dh><code>-u</code></dh><dd>[username for proxy authentication
- if required]</dd>
-<dh><code>-a</code></dh><dd>[password for proxy authentication
- if required]</dd>
+<dt><code>-H</code></dt><dd>[proxy server hostname or ip address]</dd>
+<dt><code>-P</code></dt><dd>[proxy server port]</dd>
+<dt><code>-N</code></dt><dd>[nonproxy hosts] (e.g. <code>*.apache.org|localhost</code>)</dd>
+<dt><code>-u</code></dt><dd>[username for proxy authentication
- if required]</dd>
+<dt><code>-a</code></dt><dd>[password for proxy authentication
- if required]</dd>
 </dl>
 <b>Example</b>:
 <source>jmeter -H my.proxy.server -P 8000 -u username -a password -N localhost</source>
@@ -334,17 +334,17 @@ This is not to be confused with the prox
 <p>For non-interactive testing, you may choose to run JMeter without the GUI. To do
so, use
 the following command options:</p>
 <dl>
-<dh><code>-n</code></dh><dd>This specifies JMeter is to run
in non-gui mode</dd>
-<dh><code>-t</code></dh><dd>[name of JMX file that contains
the Test Plan].</dd>
-<dh><code>-l</code></dh><dd>[name of JTL file to log sample
results to].</dd>
-<dh><code>-j</code></dh><dd>[name of JMeter run log file].</dd>
-<dh><code>-r</code></dh><dd>Run the test in the servers specified
by the JMeter property "<code>remote_hosts</code>"</dd>
-<dh><code>-R</code></dh><dd>[list of remote servers] Run the
test in the specified remote servers</dd>
+<dt><code>-n</code></dt><dd>This specifies JMeter is to run
in non-gui mode</dd>
+<dt><code>-t</code></dt><dd>[name of JMX file that contains
the Test Plan].</dd>
+<dt><code>-l</code></dt><dd>[name of JTL file to log sample
results to].</dd>
+<dt><code>-j</code></dt><dd>[name of JMeter run log file].</dd>
+<dt><code>-r</code></dt><dd>Run the test in the servers specified
by the JMeter property "<code>remote_hosts</code>"</dd>
+<dt><code>-R</code></dt><dd>[list of remote servers] Run the
test in the specified remote servers</dd>
 </dl>
 <p>The script also lets you specify the optional firewall/proxy server information:</p>
 <dl>
-<dh><code>-H</code></dh><dd>[proxy server hostname or ip address]</dd>
-<dh><code>-P</code></dh><dd>[proxy server port]</dd>
+<dt><code>-H</code></dt><dd>[proxy server hostname or ip address]</dd>
+<dt><code>-P</code></dt><dd>[proxy server port]</dd>
 </dl>
 <b>Example</b>
 <source>jmeter -n -t my_test.jmx -l log.jtl -H my.proxy.server -P 8000</source>
@@ -361,8 +361,8 @@ You can also use non-GUI mode to run rem
 To start the server(s), run <code>jmeter-server[.bat]</code> on each server host.</p>
 <p>The script also lets you specify the optional firewall/proxy server information:</p>
 <dl>
-<dh><code>-H</code></dh><dd>[proxy server hostname or ip address]</dd>
-<dh><code>-P</code></dh><dd>[proxy server port]</dd>
+<dt><code>-H</code></dt><dd>[proxy server hostname or ip address]</dd>
+<dt><code>-P</code></dt><dd>[proxy server port]</dd>
 </dl>
 <b>Example</b>:
 <source>jmeter-server -H my.proxy.server -P 8000</source>
@@ -374,9 +374,9 @@ jmeter -n -t testplan.jmx -r [-Gprop=val
 </source>
 where:
 <dl>
-<dh><code>-G</code></dh><dd>is used to define JMeter properties
to be set in the servers</dd>
-<dh><code>-X</code></dh><dd>means exit the servers at the end
of the test</dd>
-<dh><code>-Rserver1,server2</code></dh><dd>can be used instead
of <code>-r</code> to provide a list of servers to start.
+<dt><code>-G</code></dt><dd>is used to define JMeter properties
to be set in the servers</dd>
+<dt><code>-X</code></dt><dd>means exit the servers at the end
of the test</dd>
+<dt><code>-Rserver1,server2</code></dt><dd>can be used instead
of <code>-r</code> to provide a list of servers to start.
 Overrides <code>remote_hosts</code>, but does not define the property.</dd>
 </dl>
 <p>
@@ -391,11 +391,11 @@ Normally this is not necessary.
 (instead of modifying <code>jmeter.properties</code>).
 To do so, use the following options:</p>
 <dl>
-<dh><code>-D[prop_name]=[value]</code></dh><dd>defines a java
system property value.</dd>
-<dh><code>-J[prop_name]=[value]</code></dh><dd>defines a local
JMeter property.</dd>
-<dh><code>-G[prop_name]=[value]</code></dh><dd>defines a JMeter
property to be sent to all remote servers.</dd>
-<dh><code>-G[propertyfile]</code></dh><dd>defines a file containing
JMeter properties to be sent to all remote servers.</dd>
-<dh><code>-L[category]=[priority]</code></dh><dd>overrides
a logging setting, setting a particular category to the given priority level.</dd>
+<dt><code>-D[prop_name]=[value]</code></dt><dd>defines a java
system property value.</dd>
+<dt><code>-J[prop_name]=[value]</code></dt><dd>defines a local
JMeter property.</dd>
+<dt><code>-G[prop_name]=[value]</code></dt><dd>defines a JMeter
property to be sent to all remote servers.</dd>
+<dt><code>-G[propertyfile]</code></dt><dd>defines a file containing
JMeter properties to be sent to all remote servers.</dd>
+<dt><code>-L[category]=[priority]</code></dt><dd>overrides
a logging setting, setting a particular category to the given priority level.</dd>
 </dl>
 <p>The <code>-L</code> flag can also be used without the category name
to set the root logging level.</p>
 <p><b>Examples</b>:

Modified: jmeter/trunk/xdocs/usermanual/realtime-results.xml
URL: http://svn.apache.org/viewvc/jmeter/trunk/xdocs/usermanual/realtime-results.xml?rev=1700292&r1=1700291&r2=1700292&view=diff
==============================================================================
--- jmeter/trunk/xdocs/usermanual/realtime-results.xml (original)
+++ jmeter/trunk/xdocs/usermanual/realtime-results.xml Mon Aug 31 18:27:35 2015
@@ -54,45 +54,45 @@ In this document we will present the con
     Threads metrics are the following:
     </p>
     <dl>
-      <dh><code>&lt;rootMetricsPrefix&gt;.test.minAT</code></dh><dd>Min
active threads</dd>
-      <dh><code>&lt;rootMetricsPrefix&gt;.test.maxAT</code></dh><dd>Max
active threads</dd>
-      <dh><code>&lt;rootMetricsPrefix&gt;.test.meanAT</code></dh><dd>Mean
active threads</dd>
-      <dh><code>&lt;rootMetricsPrefix&gt;.test.startedT</code></dh><dd>Started
threads</dd>
-      <dh><code>&lt;rootMetricsPrefix&gt;.test.endedT</code></dh><dd>Finished
threads</dd>
+      <dt><code>&lt;rootMetricsPrefix&gt;.test.minAT</code></dt><dd>Min
active threads</dd>
+      <dt><code>&lt;rootMetricsPrefix&gt;.test.maxAT</code></dt><dd>Max
active threads</dd>
+      <dt><code>&lt;rootMetricsPrefix&gt;.test.meanAT</code></dt><dd>Mean
active threads</dd>
+      <dt><code>&lt;rootMetricsPrefix&gt;.test.startedT</code></dt><dd>Started
threads</dd>
+      <dt><code>&lt;rootMetricsPrefix&gt;.test.endedT</code></dt><dd>Finished
threads</dd>
     </dl>
     </subsection>
     <subsection name="&sect-num;.1.2 Response times metrics" anchor="metrics-response-times">
     <p>Response related metrics are the following:</p>
     <dl>
-      <dh><code>&lt;rootMetricsPrefix&gt;.&lt;samplerName&gt;.ok.count</code></dh>
+      <dt><code>&lt;rootMetricsPrefix&gt;.&lt;samplerName&gt;.ok.count</code></dt>
       <dd>Number of successful responses for sampler name</dd>
-      <dh><code>&lt;rootMetricsPrefix&gt;.&lt;samplerName&gt;.h.count</code></dh>
+      <dt><code>&lt;rootMetricsPrefix&gt;.&lt;samplerName&gt;.h.count</code></dt>
       <dd>Server hits per seconds, this metric cumulates Sample Result and Sub results
(if using Transaction Controller, "Generate parent sampler" should be unchecked)</dd>
-      <dh><code>&lt;rootMetricsPrefix&gt;.&lt;samplerName&gt;.ok.min</code></dh>
+      <dt><code>&lt;rootMetricsPrefix&gt;.&lt;samplerName&gt;.ok.min</code></dt>
       <dd>Min response time for successful responses of sampler name</dd>
-      <dh><code>&lt;rootMetricsPrefix&gt;.&lt;samplerName&gt;.ok.max</code></dh>
+      <dt><code>&lt;rootMetricsPrefix&gt;.&lt;samplerName&gt;.ok.max</code></dt>
       <dd>Max response time for successful responses of sampler name</dd>
-      <dh><code>&lt;rootMetricsPrefix&gt;.&lt;samplerName&gt;.ok.pct&lt;percentileValue&gt;</code></dh>
+      <dt><code>&lt;rootMetricsPrefix&gt;.&lt;samplerName&gt;.ok.pct&lt;percentileValue&gt;</code></dt>
       <dd>Percentile computed for successful responses of sampler name. You can input
as many percentiles as you want (3 or 4 being a reasonable value).<br/>
       When percentile contains a comma for example "<code>99.9</code>", dot is
sanitized by "<code>_</code>" leading to <code>99_9</code>.   
       By default listener computes percentiles 90%, 95% and 99%</dd>
-      <dh><code>&lt;rootMetricsPrefix&gt;.&lt;samplerName&gt;.ko.count</code></dh>
+      <dt><code>&lt;rootMetricsPrefix&gt;.&lt;samplerName&gt;.ko.count</code></dt>
       <dd>Number of failed responses for sampler name</dd>
-      <dh><code>&lt;rootMetricsPrefix&gt;.&lt;samplerName&gt;.ko.min</code></dh>
+      <dt><code>&lt;rootMetricsPrefix&gt;.&lt;samplerName&gt;.ko.min</code></dt>
       <dd>Min response time for failed responses of sampler name</dd>
-      <dh><code>&lt;rootMetricsPrefix&gt;.&lt;samplerName&gt;.ko.max</code></dh>
+      <dt><code>&lt;rootMetricsPrefix&gt;.&lt;samplerName&gt;.ko.max</code></dt>
       <dd>Max response time for failed responses of sampler name</dd>
-      <dh><code>&lt;rootMetricsPrefix&gt;.&lt;samplerName&gt;.ko.pct&lt;percentileValue&gt;</code></dh>
+      <dt><code>&lt;rootMetricsPrefix&gt;.&lt;samplerName&gt;.ko.pct&lt;percentileValue&gt;</code></dt>
       <dd>Percentile computed for failed responses of sampler name. You can input as
many percentiles as you want (3 or 4 being a reasonable value).<br/>
       When percentile contains a comma for example "<code>99.9</code>", dot is
sanitized by "<code>_</code>" leading to <code>99_9</code>.
       By default listener computes percentiles 90%, 95% and 99%</dd>
-      <dh><code>&lt;rootMetricsPrefix&gt;.&lt;samplerName&gt;.a.count</code></dh>
+      <dt><code>&lt;rootMetricsPrefix&gt;.&lt;samplerName&gt;.a.count</code></dt>
       <dd>Number of responses for sampler name</dd>
-      <dh><code>&lt;rootMetricsPrefix&gt;.&lt;samplerName&gt;.a.min</code></dh>
+      <dt><code>&lt;rootMetricsPrefix&gt;.&lt;samplerName&gt;.a.min</code></dt>
       <dd>Min response time for responses of sampler name</dd>
-      <dh><code>&lt;rootMetricsPrefix&gt;.&lt;samplerName&gt;.a.max</code></dh>
+      <dt><code>&lt;rootMetricsPrefix&gt;.&lt;samplerName&gt;.a.max</code></dt>
       <dd>Max response time for responses of sampler name</dd>
-      <dh><code>&lt;rootMetricsPrefix&gt;.&lt;samplerName&gt;.a.pct&lt;percentileValue&gt;</code></dh>
+      <dt><code>&lt;rootMetricsPrefix&gt;.&lt;samplerName&gt;.a.pct&lt;percentileValue&gt;</code></dt>
       <dd>Percentile computed for responses of sampler name. You can input as many
percentiles as you want (3 or 4 being a reasonable value).<br/>
       When percentile contains a comma for example "<code>99.9</code>", dot is
sanitized by "<code>_</code>" leading to <code>99_9</code>.
       By default listener computes percentiles 90%, 95% and 99%</dd>

Modified: jmeter/trunk/xdocs/usermanual/remote-test.xml
URL: http://svn.apache.org/viewvc/jmeter/trunk/xdocs/usermanual/remote-test.xml?rev=1700292&r1=1700291&r2=1700292&view=diff
==============================================================================
--- jmeter/trunk/xdocs/usermanual/remote-test.xml (original)
+++ jmeter/trunk/xdocs/usermanual/remote-test.xml Mon Aug 31 18:27:35 2015
@@ -126,8 +126,8 @@ jmeter -n -t script.jmx -R server1,serve
 </source>
 Other flags that may be useful:
 <dl>
-<dh><code>-Gproperty=value</code></dh><dd>define a property
in all the servers (may appear more than once)</dd>
-<dh><code>-X</code></dh><dd>Exit remote servers at the end
of the test.</dd>
+<dt><code>-Gproperty=value</code></dt><dd>define a property
in all the servers (may appear more than once)</dd>
+<dt><code>-X</code></dt><dd>Exit remote servers at the end
of the test.</dd>
 </dl>
 The first example will start the test on whatever servers are defined in the JMeter property
<code>remote_hosts</code>;<br/>
 The second example will define <code>remote_hosts</code> from the list of servers
and then start the test on the remote servers.
@@ -247,23 +247,23 @@ continue.
 There are some JMeter properties that can be set to alter this behaviour.
 </p>
 <dl>
-<dh><code>mode</code></dh><dd>sample sending mode - default
is <code>StrippedBatch</code> since 2.9. This should be set on the client node.
+<dt><code>mode</code></dt><dd>sample sending mode - default
is <code>StrippedBatch</code> since 2.9. This should be set on the client node.
     <dl>
-    <dh><code>Standard</code></dh><dd>send samples synchronously
as soon as they are generated</dd>
-    <dh><code>Hold</code></dh><dd>hold samples in an array
until the end of a run. This may use a lot of memory on the server and is discouraged.</dd>
-    <dh><code>DiskStore</code></dh><dd>store samples in a disk
file (under <code>java.io.temp</code>) until the end of a run. 
+    <dt><code>Standard</code></dt><dd>send samples synchronously
as soon as they are generated</dd>
+    <dt><code>Hold</code></dt><dd>hold samples in an array
until the end of a run. This may use a lot of memory on the server and is discouraged.</dd>
+    <dt><code>DiskStore</code></dt><dd>store samples in a disk
file (under <code>java.io.temp</code>) until the end of a run. 
     The serialised data file is deleted on JVM exit.</dd>
-    <dh><code>StrippedDiskStore</code></dh><dd>remove responseData
from successful samples, and use DiskStore sender to send them.</dd>
-    <dh><code>Batch</code></dh><dd>send saved samples when
either the count (num_sample_threshold) or time (time_threshold) exceeds a threshold,
+    <dt><code>StrippedDiskStore</code></dt><dd>remove responseData
from successful samples, and use DiskStore sender to send them.</dd>
+    <dt><code>Batch</code></dt><dd>send saved samples when
either the count (num_sample_threshold) or time (time_threshold) exceeds a threshold,
     at which point the samples are sent synchronously.
     The thresholds can be configured on the server using the following properties:
         <dl>
-        <dh><code>num_sample_threshold</code></dh><dd>number
of samples to accumulate, default <code>100</code></dd>
-        <dh><code>time_threshold</code></dh><dd>time threshold,
default 60000 ms = 60 seconds</dd>
+        <dt><code>num_sample_threshold</code></dt><dd>number
of samples to accumulate, default <code>100</code></dd>
+        <dt><code>time_threshold</code></dt><dd>time threshold,
default 60000 ms = 60 seconds</dd>
         </dl>
     
      See also the Asynch mode, described below.</dd>
-    <dh><code>Statistical</code></dh><dd>send a summary sample
when either the count or time exceeds a threshold. 
+    <dt><code>Statistical</code></dt><dd>send a summary sample
when either the count or time exceeds a threshold. 
     The samples are summarised by thread group name and sample label.
     The following fields are accumulated:
       <ul>
@@ -275,9 +275,9 @@ There are some JMeter properties that ca
       </ul>
     Other fields that vary between samples are lost. 
     </dd>
-    <dh><code>Stripped</code></dh><dd>remove responseData from
successful samples</dd>
-    <dh><code>StrippedBatch</code></dh><dd>remove responseData
from successful samples, and use Batch sender to send them.</dd>
-    <dh><code>Asynch</code></dh><dd>samples are temporarily
stored in a local queue. A separate worker thread sends the samples.
+    <dt><code>Stripped</code></dt><dd>remove responseData from
successful samples</dd>
+    <dt><code>StrippedBatch</code></dt><dd>remove responseData
from successful samples, and use Batch sender to send them.</dd>
+    <dt><code>Asynch</code></dt><dd>samples are temporarily
stored in a local queue. A separate worker thread sends the samples.
         This allows the test thread to continue without waiting for the result to be sent
back to the client.
         However, if samples are being created faster than they can be sent, the queue will
eventually fill up,
         and the sampler thread will block until some samples can be drained from the queue.
@@ -285,8 +285,8 @@ There are some JMeter properties that ca
         The queue size can be adjusted by setting the JMeter property
         <code>asynch.batch.queue.size</code> (default <code>100</code>)
on the server node.
     </dd>
-    <dh><code>StrippedAsynch</code></dh><dd>remove responseData
from successful samples, and use Async sender to send them.</dd>
-    <dh><code>Custom implementation</code></dh><dd>set the
mode parameter to your custom sample sender class name.
+    <dt><code>StrippedAsynch</code></dt><dd>remove responseData
from successful samples, and use Async sender to send them.</dd>
+    <dt><code>Custom implementation</code></dt><dd>set the
mode parameter to your custom sample sender class name.
     This must implement the interface <code>SampleSender</code> and have a constructor
which takes a single
     parameter of type <code>RemoteSampleListener</code>. 
     </dd>
@@ -299,8 +299,8 @@ This is not really a problem as there is
 </note>
 <p>The following properties apply to the <code>Batch</code> and <code>Statistical</code>
modes:</p>
     <dl>
-    <dh><code>num_sample_threshold</code></dh><dd>number of
samples in a batch (default <code>100</code>)</dd>
-    <dh><code>time_threshold</code></dh><dd>number of milliseconds
to wait (default 60 seconds)</dd>
+    <dt><code>num_sample_threshold</code></dt><dd>number of
samples in a batch (default <code>100</code>)</dd>
+    <dt><code>time_threshold</code></dt><dd>number of milliseconds
to wait (default 60 seconds)</dd>
     </dl>
 </subsection>
 



Mime
View raw message