You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@jmeter.apache.org by mi...@apache.org on 2016/04/16 16:36:02 UTC
svn commit: r1739469 [7/18] - in /jmeter/trunk: docs/ docs/css/ docs/images/
docs/images/screenshots/ docs/images/screenshots/assertion/
docs/images/screenshots/ftptest/ docs/images/screenshots/http-config/
docs/images/screenshots/jdbctest/ docs/images...
Modified: jmeter/trunk/docs/svnindex.html
URL: http://svn.apache.org/viewvc/jmeter/trunk/docs/svnindex.html?rev=1739469&r1=1739468&r2=1739469&view=diff
==============================================================================
--- jmeter/trunk/docs/svnindex.html (original)
+++ jmeter/trunk/docs/svnindex.html Sat Apr 16 14:36:00 2016
@@ -1,23 +1,12 @@
<!DOCTYPE html SYSTEM "about:legacy-compat">
<html lang="en"><head><META http-equiv="Content-Type" content="text/html; charset=iso-8859-15"><title>Apache JMeter
-
- Source Repositories</title><meta name="author" value="Apache JMeter Project"><meta name="email" value="dev.AT.jmeter.DOT.apache.DOT.org"><meta name="viewport" content="width=device-width, initial-scale=1"><link href="http://fonts.googleapis.com/css?family=Merriweather:400normal" rel="stylesheet" type="text/css"><link rel="stylesheet" type="text/css" href="./css/new-style.css"></head><body role="document"><a href="#content" class="hidden">Main content</a><div class="header"><!--
+ Source Repositories</title><meta name="author" value="Apache JMeter Project"><meta name="email" value="dev.AT.jmeter.DOT.apache.DOT.org"><meta name="viewport" content="width=device-width, initial-scale=1"><link href="http://fonts.googleapis.com/css?family=Merriweather:400normal" rel="stylesheet" type="text/css"><link rel="stylesheet" type="text/css" href="./css/new-style.css"><link rel="apple-touch-icon-precomposed" href="./images/apple-touch-icon.png"><link rel="icon" href="./images/favicon.png"><meta name="msapplication-TileColor" content="#ffffff"><meta name="msapplication-TileImage" content="./images/mstile-144x144.png"><meta name="theme-color" content="#ffffff"></head><body role="document"><a href="#content" class="hidden">Main content</a><div class="header"><!--
APACHE LOGO
- --><div><a href="http://www.apache.org"><img title="Apache Software Foundation" width="290" height="75" src="./images/asf-logo.png" alt="Logo ASF"></a></div><!--
+ --><div><a href="http://www.apache.org"><img title="Apache Software Foundation" class="logo" src="./images/asf-logo.svg" alt="Logo ASF"></a></div><!--
PROJECT LOGO
- --><div><a href="http://jmeter.apache.org/"><img src="./images/logo.jpg" alt="Apache JMeter"></a></div><div class="twitter"><div><a href="https://twitter.com/share" class="twitter-share-button" data-text="Powerful Load Testing with Apache #JMeter" data-via="ApacheJMeter" data-lang="en-gb" data-size="large">Tweet</a><script>
- (function(d,s,id){
- var js,
- fjs=d.getElementsByTagName(s)[0],
- p=/^http:/.test(d.location)?'http':'https';
- if (!d.getElementById(id)) {
- js=d.createElement(s);
- js.id=id;
- js.src=p+'://platform.twitter.com/widgets.js';
- fjs.parentNode.insertBefore(js,fjs);
- }
- })(document, 'script', 'twitter-wjs');
- </script></div><div><a href="https://twitter.com/ApacheJMeter" class="twitter-follow-button" data-show-count="false" data-lang="en-gb" data-size="large">Follow</a><script>(function(d,s,id){
+ --><div><a href="http://jmeter.apache.org/"><img class="logo" src="./images/logo.svg" alt="Apache JMeter"></a></div><div class="banner"><iframe src="http://www.apache.org/ads/bannerbar.html" style="border-width:0;" frameborder="0" scrolling="no"></iframe><div class="clear"></div></div></div><div class="nav"><div class="social menu"><div><a href="https://twitter.com/share" class="twitter-share-button" data-text="Powerful Load Testing with Apache #JMeter" data-via="ApacheJMeter" data-lang="en-gb" data-size="large">Tweet</a><script>
+ (function(d,s,id){
var js,
fjs=d.getElementsByTagName(s)[0],
p=/^http:/.test(d.location)?'http':'https';
@@ -27,14 +16,25 @@
js.src=p+'://platform.twitter.com/widgets.js';
fjs.parentNode.insertBefore(js,fjs);
}
- })(document, 'script', 'twitter-wjs');
- </script></div></div><div class="banner"><iframe src="http://www.apache.org/ads/bannerbar.html" style="border-width:0;" frameborder="0" scrolling="no"></iframe><div class="clear"></div></div></div><div class="nav"><ul class="menu"><li><div class="menu-title">About</div><ul><li><a href="./index.html">Overview</a></li><li><a href="http://twitter.com/ApacheJMeter">JMeter on Twitter<img src="./images/twitter.png" alt="Icon for JMeter on Twitter"></a></li><li><a href="./issues.html">Issue Tracking</a></li><li><a href="http://projects.apache.org/feeds/rss/jmeter.xml">Subscribe to What's New</a></li><li><a href="http://www.apache.org/licenses/">License</a></li></ul></li></ul><ul class="menu"><li><div class="menu-title">Download</div><ul><li><a href="./download_jmeter.cgi">Download Releases</a></li><li><a href="./nightly.html">Developer (Nightly) Builds</a></li></ul></li></ul><ul class="menu"><li><div class="menu-title">Documentation</div><ul><li><a href="./changes.html">Chang
es per version</a></li><li><a href="./usermanual/get-started.html">Get Started</a></li><li><a href="./usermanual/index.html">User Manual</a></li><li><a href="./usermanual/best-practices.html">Best Practices</a></li><li><a href="./usermanual/component_reference.html">Component Reference</a></li><li><a href="./usermanual/functions.html">Functions Reference</a></li><li><a href="./api/index.html">Javadocs</a></li><li><a href="./building.html">Building JMeter and Add-Ons</a></li><li><a href="http://wiki.apache.org/jmeter">JMeter Wiki</a></li><li><a href="http://wiki.apache.org/jmeter/JMeterFAQ">FAQ (Wiki)</a></li></ul></li></ul><ul class="menu"><li><div class="menu-title">Tutorials (PDF format)</div><ul><li><a href="./usermanual/jmeter_distributed_testing_step_by_step.pdf">Distributed Testing</a></li><li><a href="./usermanual/jmeter_proxy_step_by_step.pdf">Recording Tests</a></li><li><a href="./usermanual/junitsampler_tutorial.pdf">JUnit Sampler</a></li><li><a href="./usermanual/jmeter_a
ccesslog_sampler_step_by_step.pdf">Access Log Sampler</a></li><li><a href="./extending/jmeter_tutorial.pdf">Extending JMeter</a></li></ul></li></ul><ul class="menu"><li><div class="menu-title">Community</div><ul><li><a href="http://wiki.apache.org/jmeter/JMeterCommitters">Contributors</a></li><li><a href="./mail.html">Mailing Lists</a></li><li><a href="./svnindex.html">SVN Repositories</a></li></ul></li></ul><ul class="menu"><li><div class="menu-title">Foundation</div><ul><li><a href="http://www.apache.org/">ASF</a></li><li><a href="http://www.apache.org/foundation/getinvolved.html">Get Involved in the ASF</a></li><li><a href="http://www.apache.org/foundation/sponsorship.html">Sponsorship</a></li><li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li></ul></li></ul></div><div class="main" id="content"><div class="section"><h1>Download the Source</h1>
+ })(document, 'script', 'twitter-wjs');
+ </script></div><div><a href="https://twitter.com/ApacheJMeter" class="twitter-follow-button" data-show-count="false" data-lang="en-gb" data-size="large">Follow</a><script>(function(d,s,id){
+ var js,
+ fjs=d.getElementsByTagName(s)[0],
+ p=/^http:/.test(d.location)?'http':'https';
+ if (!d.getElementById(id)) {
+ js=d.createElement(s);
+ js.id=id;
+ js.src=p+'://platform.twitter.com/widgets.js';
+ fjs.parentNode.insertBefore(js,fjs);
+ }
+ })(document, 'script', 'twitter-wjs');
+ </script></div><div><a href="https://github.com/apache/jmeter"><img alt="star this repo" src="http://githubbadges.com/star.svg?user=apache&repo=jmeter&style=default"></a></div><div><a href="https://github.com/apache/jmeter/fork"><img alt="fork this repo" src="http://githubbadges.com/fork.svg?user=apache&repo=jmeter&style=default"></a></div><div><a href="https://maven-badges.herokuapp.com/maven-central/org.apache.jmeter/ApacheJMeter"><img alt="Maven Central" src="https://maven-badges.herokuapp.com/maven-central/org.apache.jmeter/ApacheJMeter/badge.png"></a></div></div><ul class="menu"><li onClick="return true"><div class="menu-title">About</div><ul><li><a href="./index.html">Overview</a></li><li><a href="http://www.apache.org/licenses/">License</a></li></ul></li></ul><ul class="menu"><li onClick="return true"><div class="menu-title">Download</div><ul><li><a href="./download_jmeter.cgi">Download Releases</a></li><li><a href="./nightly.html">Developer (N
ightly) Builds</a></li></ul></li></ul><ul class="menu"><li onClick="return true"><div class="menu-title">Documentation</div><ul><li><a href="./changes.html">Changes per version</a></li><li><a href="./usermanual/get-started.html">Get Started</a></li><li><a href="./usermanual/index.html">User Manual</a></li><li><a href="./usermanual/best-practices.html">Best Practices</a></li><li><a href="./usermanual/component_reference.html">Component Reference</a></li><li><a href="./usermanual/functions.html">Functions Reference</a></li><li><a href="./api/index.html">Javadocs</a></li><li><a href="./building.html">Building JMeter and Add-Ons</a></li><li><a href="http://wiki.apache.org/jmeter">JMeter Wiki</a></li><li><a href="http://wiki.apache.org/jmeter/JMeterFAQ">FAQ (Wiki)</a></li></ul></li></ul><ul class="menu"><li onClick="return true"><div class="menu-title">Tutorials (PDF format)</div><ul><li><a href="./usermanual/jmeter_distributed_testing_step_by_step.pdf">Distributed Testing</a></li><li><a
href="./usermanual/jmeter_proxy_step_by_step.pdf">Recording Tests</a></li><li><a href="./usermanual/junitsampler_tutorial.pdf">JUnit Sampler</a></li><li><a href="./usermanual/jmeter_accesslog_sampler_step_by_step.pdf">Access Log Sampler</a></li><li><a href="./extending/jmeter_tutorial.pdf">Extending JMeter</a></li></ul></li></ul><ul class="menu"><li onClick="return true"><div class="menu-title">Community</div><ul><li><a href="./issues.html">Issue Tracking</a></li><li><a href="./mail.html">Mailing Lists</a></li><li><a href="./svnindex.html">Source Repositories</a></li><li><a href="./building.html">Building and Contributing</a></li><li><a href="https://projects.apache.org/project.html?jmeter">Project info at Apache</a></li><li><a href="http://wiki.apache.org/jmeter/JMeterCommitters">Contributors</a></li></ul></li></ul><ul class="menu"><li onClick="return true"><div class="menu-title">Foundation</div><ul><li><a href="http://www.apache.org/">ASF</a></li><li><a href="http://www.apache.o
rg/foundation/getinvolved.html">Get Involved in the ASF</a></li><li><a href="http://www.apache.org/foundation/sponsorship.html">Sponsorship</a></li><li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li></ul></li></ul></div><div class="main" id="content"><div class="section"><h1>Download the Source</h1>
<p>Most users of the source code probably don't need to have day to
day access to the source code as it changes. For these users we
provide easy to unpack source code downloads via our <a href="download_jmeter.cgi">download page</a>. </p>
-</div><div class="section"><h1>Access the Version Controlled Source Code</h1>
+</div><div class="section"><h1>Access the SVN Version Controlled Source Code</h1>
<p>For information on connecting to the ASF Subversion repositories, see the <a href="http://www.apache.org/dev/version-control.html">version control
page</a>. </p>
@@ -42,7 +42,7 @@ page</a>. </p>
<p>Modules available for access are listed below.</p>
-<div class="subsection"><h2>Subversion<a class="sectionlink" href="#subversion" title="Link to here">¶</a></h2>
+<div class="subsection"><h2 id="subversion">Subversion<a class="sectionlink" href="#subversion" title="Link to here">¶</a></h2>
<p><a href="http://subversion.apache.org">Subversion</a> is an open-source version control system. The root url of the
ASF Subversion repository is <a href="http://svn.apache.org/repos/asf/">http://svn.apache.org/repos/asf/</a> for non-committers and <a href="https://svn.apache.org/repos/asf/">https://svn.apache.org/repos/asf/</a> for committers. </p>
@@ -66,11 +66,34 @@ When checking out a subproject using Sub
</table>
</div>
+</div><div class="section"><h1>Access the GIT Version Controlled Source Code</h1>
+
+<p>For information on connecting to the GIT mirror repositories, see the <a href="http://www.apache.org/dev/git.html">version control
+page</a>. </p>
+
+<div class="subsection"><h2 id="git">Git<a class="sectionlink" href="#git" title="Link to here">¶</a></h2>
+
+<p>Apache maintains read-only GIT mirrors of Apache codebases, for JMeter, the mirror is accessible at the urls below.</p>
+
+<table>
+ <tr>
+ <th>Project</th>
+ <th>GIT (read-only)</th>
+ <th>GITHUB (read-only)</th>
+ </tr>
+ <tr>
+ <td>Apache JMeter</td>
+ <td><a href="git://git.apache.org/jmeter.git">git://git.apache.org/jmeter.git</a></td>
+ <td><a href="https://github.com/apache/jmeter">https://github.com/apache/jmeter</a></td>
+ </tr>
+</table>
+
+</div>
</div></div><div class="footer"><div class="copyright">
Copyright ©
1999 –
- 2015
+ 2016
, Apache Software Foundation
</div><div class="trademarks">Apache, Apache JMeter, JMeter, the Apache
feather, and the Apache JMeter logo are
Modified: jmeter/trunk/docs/usermanual/best-practices.html
URL: http://svn.apache.org/viewvc/jmeter/trunk/docs/usermanual/best-practices.html?rev=1739469&r1=1739468&r2=1739469&view=diff
==============================================================================
--- jmeter/trunk/docs/usermanual/best-practices.html (original)
+++ jmeter/trunk/docs/usermanual/best-practices.html Sat Apr 16 14:36:00 2016
@@ -1,23 +1,12 @@
<!DOCTYPE html SYSTEM "about:legacy-compat">
<html lang="en"><head><META http-equiv="Content-Type" content="text/html; charset=iso-8859-15"><title>Apache JMeter
-
- User's Manual: Best Practices</title><meta name="viewport" content="width=device-width, initial-scale=1"><link href="http://fonts.googleapis.com/css?family=Merriweather:400normal" rel="stylesheet" type="text/css"><link rel="stylesheet" type="text/css" href="../css/new-style.css"></head><body role="document"><a href="#content" class="hidden">Main content</a><div class="header"><!--
+ User's Manual: Best Practices</title><meta name="viewport" content="width=device-width, initial-scale=1"><link href="http://fonts.googleapis.com/css?family=Merriweather:400normal" rel="stylesheet" type="text/css"><link rel="stylesheet" type="text/css" href="../css/new-style.css"><link rel="apple-touch-icon-precomposed" href="../images/apple-touch-icon.png"><link rel="icon" href="../images/favicon.png"><meta name="msapplication-TileColor" content="#ffffff"><meta name="msapplication-TileImage" content="../images/mstile-144x144.png"><meta name="theme-color" content="#ffffff"></head><body role="document"><a href="#content" class="hidden">Main content</a><div class="header"><!--
APACHE LOGO
- --><div><a href="http://www.apache.org"><img title="Apache Software Foundation" width="290" height="75" src="../images/asf-logo.png" alt="Logo ASF"></a></div><!--
+ --><div><a href="http://www.apache.org"><img title="Apache Software Foundation" class="logo" src="../images/asf-logo.svg" alt="Logo ASF"></a></div><!--
PROJECT LOGO
- --><div><a href="http://jmeter.apache.org/"><img src="../images/logo.jpg" alt="Apache JMeter"></a></div><div class="twitter"><div><a href="https://twitter.com/share" class="twitter-share-button" data-text="Powerful Load Testing with Apache #JMeter" data-via="ApacheJMeter" data-lang="en-gb" data-size="large">Tweet</a><script>
- (function(d,s,id){
- var js,
- fjs=d.getElementsByTagName(s)[0],
- p=/^http:/.test(d.location)?'http':'https';
- if (!d.getElementById(id)) {
- js=d.createElement(s);
- js.id=id;
- js.src=p+'://platform.twitter.com/widgets.js';
- fjs.parentNode.insertBefore(js,fjs);
- }
- })(document, 'script', 'twitter-wjs');
- </script></div><div><a href="https://twitter.com/ApacheJMeter" class="twitter-follow-button" data-show-count="false" data-lang="en-gb" data-size="large">Follow</a><script>(function(d,s,id){
+ --><div><a href="http://jmeter.apache.org/"><img class="logo" src="../images/logo.svg" alt="Apache JMeter"></a></div><div class="banner"><iframe src="http://www.apache.org/ads/bannerbar.html" style="border-width:0;" frameborder="0" scrolling="no"></iframe><div class="clear"></div></div></div><div class="nav"><div class="social menu"><div><a href="https://twitter.com/share" class="twitter-share-button" data-text="Powerful Load Testing with Apache #JMeter" data-via="ApacheJMeter" data-lang="en-gb" data-size="large">Tweet</a><script>
+ (function(d,s,id){
var js,
fjs=d.getElementsByTagName(s)[0],
p=/^http:/.test(d.location)?'http':'https';
@@ -27,14 +16,25 @@
js.src=p+'://platform.twitter.com/widgets.js';
fjs.parentNode.insertBefore(js,fjs);
}
- })(document, 'script', 'twitter-wjs');
- </script></div></div><div class="banner"><iframe src="http://www.apache.org/ads/bannerbar.html" style="border-width:0;" frameborder="0" scrolling="no"></iframe><div class="clear"></div></div></div><div class="nav"><ul class="menu"><li><div class="menu-title">About</div><ul><li><a href="../index.html">Overview</a></li><li><a href="http://twitter.com/ApacheJMeter">JMeter on Twitter<img src="../images/twitter.png" alt="Icon for JMeter on Twitter"></a></li><li><a href="../issues.html">Issue Tracking</a></li><li><a href="http://projects.apache.org/feeds/rss/jmeter.xml">Subscribe to What's New</a></li><li><a href="http://www.apache.org/licenses/">License</a></li></ul></li></ul><ul class="menu"><li><div class="menu-title">Download</div><ul><li><a href="../download_jmeter.cgi">Download Releases</a></li><li><a href="../nightly.html">Developer (Nightly) Builds</a></li></ul></li></ul><ul class="menu"><li><div class="menu-title">Documentation</div><ul><li><a href="../changes.html"
>Changes per version</a></li><li><a href="../usermanual/get-started.html">Get Started</a></li><li><a href="../usermanual/index.html">User Manual</a></li><li><a href="../usermanual/best-practices.html">Best Practices</a></li><li><a href="../usermanual/component_reference.html">Component Reference</a></li><li><a href="../usermanual/functions.html">Functions Reference</a></li><li><a href="../api/index.html">Javadocs</a></li><li><a href="../building.html">Building JMeter and Add-Ons</a></li><li><a href="http://wiki.apache.org/jmeter">JMeter Wiki</a></li><li><a href="http://wiki.apache.org/jmeter/JMeterFAQ">FAQ (Wiki)</a></li></ul></li></ul><ul class="menu"><li><div class="menu-title">Tutorials (PDF format)</div><ul><li><a href="../usermanual/jmeter_distributed_testing_step_by_step.pdf">Distributed Testing</a></li><li><a href="../usermanual/jmeter_proxy_step_by_step.pdf">Recording Tests</a></li><li><a href="../usermanual/junitsampler_tutorial.pdf">JUnit Sampler</a></li><li><a href="../us
ermanual/jmeter_accesslog_sampler_step_by_step.pdf">Access Log Sampler</a></li><li><a href="../extending/jmeter_tutorial.pdf">Extending JMeter</a></li></ul></li></ul><ul class="menu"><li><div class="menu-title">Community</div><ul><li><a href="http://wiki.apache.org/jmeter/JMeterCommitters">Contributors</a></li><li><a href="../mail.html">Mailing Lists</a></li><li><a href="../svnindex.html">SVN Repositories</a></li></ul></li></ul><ul class="menu"><li><div class="menu-title">Foundation</div><ul><li><a href="http://www.apache.org/">ASF</a></li><li><a href="http://www.apache.org/foundation/getinvolved.html">Get Involved in the ASF</a></li><li><a href="http://www.apache.org/foundation/sponsorship.html">Sponsorship</a></li><li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li></ul></li></ul></div><div class="main" id="content"><ul class="pagelinks"><li><a href="remote-test.html">< Prev</a></li><li><a href="../index.html">Index</a></li><li><a href="boss.html">Next >
;</a></li></ul><div class="section"><h1 id="best_practices">16. Best Practices<a class="sectionlink" href="#best_practices" title="Link to here">¶</a></h1>
-</div><div class="section"><h1 id="use_latest_version">16.1 Always use latest version of JMeter<a class="sectionlink" href="#use_latest_version" title="Link to here">¶</a></h1>
+ })(document, 'script', 'twitter-wjs');
+ </script></div><div><a href="https://twitter.com/ApacheJMeter" class="twitter-follow-button" data-show-count="false" data-lang="en-gb" data-size="large">Follow</a><script>(function(d,s,id){
+ var js,
+ fjs=d.getElementsByTagName(s)[0],
+ p=/^http:/.test(d.location)?'http':'https';
+ if (!d.getElementById(id)) {
+ js=d.createElement(s);
+ js.id=id;
+ js.src=p+'://platform.twitter.com/widgets.js';
+ fjs.parentNode.insertBefore(js,fjs);
+ }
+ })(document, 'script', 'twitter-wjs');
+ </script></div><div><a href="https://github.com/apache/jmeter"><img alt="star this repo" src="http://githubbadges.com/star.svg?user=apache&repo=jmeter&style=default"></a></div><div><a href="https://github.com/apache/jmeter/fork"><img alt="fork this repo" src="http://githubbadges.com/fork.svg?user=apache&repo=jmeter&style=default"></a></div><div><a href="https://maven-badges.herokuapp.com/maven-central/org.apache.jmeter/ApacheJMeter"><img alt="Maven Central" src="https://maven-badges.herokuapp.com/maven-central/org.apache.jmeter/ApacheJMeter/badge.png"></a></div></div><ul class="menu"><li onClick="return true"><div class="menu-title">About</div><ul><li><a href="../index.html">Overview</a></li><li><a href="http://www.apache.org/licenses/">License</a></li></ul></li></ul><ul class="menu"><li onClick="return true"><div class="menu-title">Download</div><ul><li><a href="../download_jmeter.cgi">Download Releases</a></li><li><a href="../nightly.html">Developer
(Nightly) Builds</a></li></ul></li></ul><ul class="menu"><li onClick="return true"><div class="menu-title">Documentation</div><ul><li><a href="../changes.html">Changes per version</a></li><li><a href="../usermanual/get-started.html">Get Started</a></li><li><a href="../usermanual/index.html">User Manual</a></li><li><a href="../usermanual/best-practices.html">Best Practices</a></li><li><a href="../usermanual/component_reference.html">Component Reference</a></li><li><a href="../usermanual/functions.html">Functions Reference</a></li><li><a href="../api/index.html">Javadocs</a></li><li><a href="../building.html">Building JMeter and Add-Ons</a></li><li><a href="http://wiki.apache.org/jmeter">JMeter Wiki</a></li><li><a href="http://wiki.apache.org/jmeter/JMeterFAQ">FAQ (Wiki)</a></li></ul></li></ul><ul class="menu"><li onClick="return true"><div class="menu-title">Tutorials (PDF format)</div><ul><li><a href="../usermanual/jmeter_distributed_testing_step_by_step.pdf">Distributed Testing</a
></li><li><a href="../usermanual/jmeter_proxy_step_by_step.pdf">Recording Tests</a></li><li><a href="../usermanual/junitsampler_tutorial.pdf">JUnit Sampler</a></li><li><a href="../usermanual/jmeter_accesslog_sampler_step_by_step.pdf">Access Log Sampler</a></li><li><a href="../extending/jmeter_tutorial.pdf">Extending JMeter</a></li></ul></li></ul><ul class="menu"><li onClick="return true"><div class="menu-title">Community</div><ul><li><a href="../issues.html">Issue Tracking</a></li><li><a href="../mail.html">Mailing Lists</a></li><li><a href="../svnindex.html">Source Repositories</a></li><li><a href="../building.html">Building and Contributing</a></li><li><a href="https://projects.apache.org/project.html?jmeter">Project info at Apache</a></li><li><a href="http://wiki.apache.org/jmeter/JMeterCommitters">Contributors</a></li></ul></li></ul><ul class="menu"><li onClick="return true"><div class="menu-title">Foundation</div><ul><li><a href="http://www.apache.org/">ASF</a></li><li><a href=
"http://www.apache.org/foundation/getinvolved.html">Get Involved in the ASF</a></li><li><a href="http://www.apache.org/foundation/sponsorship.html">Sponsorship</a></li><li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li></ul></li></ul></div><div class="main" id="content"><ul class="pagelinks"><li><a href="realtime-results.html">< Prev</a></li><li><a href="../index.html">Index</a></li><li><a href="boss.html">Next ></a></li></ul><div class="section"><h1 id="best_practices">18. Best Practices<a class="sectionlink" href="#best_practices" title="Link to here">¶</a></h1>
+</div><div class="section"><h1 id="use_latest_version">18.1 Always use latest version of JMeter<a class="sectionlink" href="#use_latest_version" title="Link to here">¶</a></h1>
<p>The performance of JMeter is being constantly improved, so users are highly encouraged to use the most up to date version. <br>
Ensure you always read <a href="../changes.html">changes list</a> to be aware of new improvements and components.
You should absolutely avoid using versions that are older than 3 versions before the last one.
</p>
-</div><div class="section"><h1 id="sizing_threads">16.2 Use the correct Number of Threads<a class="sectionlink" href="#sizing_threads" title="Link to here">¶</a></h1>
+</div><div class="section"><h1 id="sizing_threads">18.2 Use the correct Number of Threads<a class="sectionlink" href="#sizing_threads" title="Link to here">¶</a></h1>
<p>Your hardware capabilities as well as the Test Plan design will both impact the number of threads you can effectively
run with JMeter. The number will also depend on how fast your server is (a faster server
makes JMeter work harder since it returns a response quicker). As with any Load Testing tool, if you don't correctly size
@@ -46,25 +46,24 @@ For testing how JMeter performs on a giv
It does not require any network access so can give some idea as to the maximum throughput achievable.
</p>
<p>
-JMeter versions since 2.8 have an option to delay thread creation until the thread
-starts sampling, i.e. after any thread group delay and the ramp-up time for the thread itself.
+JMeter has an option to delay thread creation until the thread starts sampling, i.e. after any thread group delay and the ramp-up time for the thread itself.
This allows for a very large total number of threads, provided that not too many are active concurrently.
</p>
-</div><div class="section"><h1 id="put_cookie_manager">16.3 Where to Put the Cookie Manager<a class="sectionlink" href="#put_cookie_manager" title="Link to here">¶</a></h1>
+</div><div class="section"><h1 id="put_cookie_manager">18.3 Where to Put the Cookie Manager<a class="sectionlink" href="#put_cookie_manager" title="Link to here">¶</a></h1>
<p>See <a href="build-web-test-plan.html#adding_cookie_support">Building a Web Test</a>
for information.</p>
-</div><div class="section"><h1 id="put_auth_manager">16.4 Where to Put the Authorization Manager<a class="sectionlink" href="#put_auth_manager" title="Link to here">¶</a></h1>
+</div><div class="section"><h1 id="put_auth_manager">18.4 Where to Put the Authorization Manager<a class="sectionlink" href="#put_auth_manager" title="Link to here">¶</a></h1>
<p>See <a href="build-adv-web-test-plan.html#header_manager">Building an Advanced
Web Test</a> for information.</p>
-</div><div class="section"><h1 id="proxy_server">16.5 Using the HTTP(S) Test Script Recorder<a class="sectionlink" href="#proxy_server" title="Link to here">¶</a></h1>
+</div><div class="section"><h1 id="proxy_server">18.5 Using the HTTP(S) Test Script Recorder<a class="sectionlink" href="#proxy_server" title="Link to here">¶</a></h1>
<p>Refer to <a href="../usermanual/component_reference.html#HTTP(S)_Test_Script_Recorder">HTTP(S) Test Script Recorder</a> for details on setting up the
recorder. 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
be instructed to download all images on a page - see <a href="../usermanual/component_reference.html#HTTP_Request">HTTP Request</a>).
These will just clutter your test plan. Most likely, there is an extension all your files
-share, such as .jsp, .asp, .php, .html or the like. These you should "include" by
-entering ".*\.jsp" as an "Include Pattern". </p>
-<p>Alternatively, you can exclude images by entering ".*\.gif" as an "Exclude Pattern".
+share, such as <span class="code">.jsp</span>, <span class="code">.asp</span>, <span class="code">.php</span>, <span class="code">.html</span> or the like.
+These you should "<span class="code">include</span>" by entering "<span class="code">.*\.jsp</span>" as an "Include Pattern". </p>
+<p>Alternatively, you can exclude images by entering "<span class="code">.*\.gif</span>" as an "Exclude Pattern".
Depending on your application, this may or may not be a better way to go. You may
also have to exclude stylesheets, javascript files, and other included files. Test
out your settings to verify you are recording what you want, and then erase and start
@@ -83,9 +82,9 @@ certain common elements from the recorde
<a href="functions.html">user-defined variables</a> at the Test Plan level or in
<a href="../usermanual/component_reference.html#User_Defined_Variables">User Defined Variables</a> elements, you can have JMeter automatically
replace values in you recorded samples. For instance, if you are testing an app on
-server "xxx.example.com", then you can define a variable called "server" with the value of
-"xxx.example.com", and anyplace that value is found in your recorded samples will be replaced
-with "${server}".
+server "<span class="code">xxx.example.com</span>", then you can define a variable called "<span class="code">server</span>" with the value of
+"<span class="code">xxx.example.com</span>", and anyplace that value is found in your recorded samples will be replaced
+with "<span class="code">${server}</span>".
<div class="clear"></div><div class="note">Please note that matching is case-sensitive.</div><div class="clear"></div>
@@ -93,15 +92,15 @@ with "${server}".
<p>
If JMeter does not record any samples, check that the browser really is using the proxy.
If the browser works OK even if JMeter is not running, then the browser cannot be using the proxy.
-Some browsers ignore proxy settings for localhost or 127.0.0.1; try using the local hostname or IP instead.
+Some browsers ignore proxy settings for <span class="code">localhost</span> or <span class="code">127.0.0.1</span>; try using the local hostname or IP instead.
</p>
<p>
-The error "unknown_ca" probably means that you are trying to record HTTPS, and the browser has not accepted the
-JMeter Proxy server certificate.
+The error "<span class="code">unknown_ca</span>" probably means that you are trying to record HTTPS, and the browser has not accepted the
+JMeter Proxy server certificate.
</p>
-</div><div class="section"><h1 id="user_variables">16.6 User variables<a class="sectionlink" href="#user_variables" title="Link to here">¶</a></h1>
+</div><div class="section"><h1 id="user_variables">18.6 User variables<a class="sectionlink" href="#user_variables" title="Link to here">¶</a></h1>
<p>
Some test plans need to use different values for different users/threads.
For example, you might want to test a sequence that requires a unique login for each user.
@@ -114,25 +113,25 @@ Put this in the same directory as your t
</li>
<li>
Add a CSV DataSet configuration element to the test plan.
-Name the variables USER and PASS.
+Name the variables <span class="code">USER</span> and <span class="code">PASS</span>.
</li>
<li>
-Replace the login name with ${USER} and the password with ${PASS} on the appropriate
+Replace the login name with <span class="code">${USER}</span> and the password with <span class="code">${PASS}</span> on the appropriate
samplers
</li>
</ul>
-<p>The CSV Data Set element will read a new line for each thread.
+<p>The CSV Data Set element will read a new line for each thread.
</p>
-</div><div class="section"><h1 id="lean_mean">16.7 Reducing resource requirements<a class="sectionlink" href="#lean_mean" title="Link to here">¶</a></h1>
+</div><div class="section"><h1 id="lean_mean">18.7 Reducing resource requirements<a class="sectionlink" href="#lean_mean" title="Link to here">¶</a></h1>
<p>
Some suggestions on reducing resource usage.
</p>
<ul>
-<li>Use non-GUI mode: jmeter -n -t test.jmx -l test.jtl</li>
-<li>Use as few Listeners as possible; if using the -l flag as above they can all be deleted or disabled.</li>
+<li>Use non-GUI mode: <span class="code">jmeter -n -t test.jmx -l test.jtl</span></li>
+<li>Use as few Listeners as possible; if using the <span class="code">-l</span> flag as above they can all be deleted or disabled.</li>
<li>Don't use "View Results Tree" or "View Results in Table" listeners during the load test, use them only during scripting phase to debug your scripts.</li>
-<li>Rather than using lots of similar samplers,
-use the same sampler in a loop, and use variables (CSV Data Set) to vary the sample.
+<li>Rather than using lots of similar samplers,
+use the same sampler in a loop, and use variables (CSV Data Set) to vary the sample.
[The Include Controller does not help here, as it adds all the test elements in the file to the test plan.]
</li>
<li>Don't use functional mode</li>
@@ -143,9 +142,9 @@ use the same sampler in a loop, and use
</ul>
<p>
If your test needs large amounts of data - particularly if it needs to be randomised - create the test data in a file
-that can be read with CSV Dataset. This avoids wasting resources at run-time.
+that can be read with CSV Dataset. This avoids wasting resources at run-time.
</p>
-</div><div class="section"><h1 id="beanshell_server">16.8 BeanShell server<a class="sectionlink" href="#beanshell_server" title="Link to here">¶</a></h1>
+</div><div class="section"><h1 id="beanshell_server">18.8 BeanShell server<a class="sectionlink" href="#beanshell_server" title="Link to here">¶</a></h1>
<p>
The BeanShell interpreter has a very useful feature - it can act as a server,
which is accessible by telnet or http.
@@ -156,36 +155,36 @@ These can provide unrestricted access to
<b>Do not enable the server unless the ports are protected against access, e.g. by a firewall.</b>
</div><div class="clear"></div>
<p>
-If you do wish to use the server, define the following in jmeter.properties:
+If you do wish to use the server, define the following in <span class="code">jmeter.properties</span>:
</p>
-<pre>
+<pre class="source">
beanshell.server.port=9000
beanshell.server.file=../extras/startup.bsh
</pre>
<p>
-In the above example, the server will be started, and will listen on ports 9000 and 9001.
-Port 9000 will be used for http access. Port 9001 will be used for telnet access.
-The startup.bsh file will be processed by the server, and can be used to define various functions and set up variables.
+In the above example, the server will be started, and will listen on ports <span class="code">9000</span> and <span class="code">9001</span>.
+Port <span class="code">9000</span> will be used for http access. Port <span class="code">9001</span> will be used for telnet access.
+The <span class="code">startup.bsh</span> file will be processed by the server, and can be used to define various functions and set up variables.
The startup file defines methods for setting and printing JMeter and system properties.
This is what you should see in the JMeter console:
</p>
-<pre>
+<pre class="source">
Startup script running
Startup script completed
Httpd started on port: 9000
-Sessiond started on port: 9001
+Session started on port: 9001
</pre>
<p>
-There is a sample script (extras/remote.bsh) you can use to test the server.
+There is a sample script (<span class="code">extras/remote.bsh</span>) you can use to test the server.
[Have a look at it to see how it works.]
<br>
-When starting it in the JMeter bin directory
+When starting it in the JMeter <span class="code">bin</span> directory
(adjust paths as necessary if running from elsewhere)
the output should look like:
-<pre>
+<pre class="source">
$ java -jar ../lib/bshclient.jar localhost 9000 ../extras/remote.bsh
Connecting to BSH server on localhost:9000
-Reading responses from server ...
+Reading responses from server …
BeanShell 2.0b5 - by Pat Niemeyer (pat@pat.net)
bsh % remote.bsh starting
user.home = C:\Documents and Settings\User
@@ -204,42 +203,42 @@ Setting property 'EXAMPLE' to '8'.
Setting property 'EXAMPLE' to '9'.
EXAMPLE = 9
remote.bsh ended
-bsh % ... disconnected from server.
+bsh % … disconnected from server.
</pre>
</p>
<p>
As a practical example, assume you have a long-running JMeter test running in non-GUI mode,
-and you want to vary the throughput at various times during the test.
+and you want to vary the throughput at various times during the test.
The test-plan includes a Constant Throughput Timer which is defined in terms of a property,
-e.g. ${__P(throughput)}.
+e.g. <span class="code">${__P(throughput)}</span>.
The following BeanShell commands could be used to change the test:
</p>
-<pre>
+<pre class="source">
printprop("throughput");
-curr=Integer.decode(args[0]); // Start value
-inc=Integer.decode(args[1]); // Increment
-end=Integer.decode(args[2]); // Final value
-secs=Integer.decode(args[3]); // Wait between changes
-while(curr <= end){
+curr = Integer.decode(args[0]); // Start value
+inc = Integer.decode(args[1]); // Increment
+end = Integer.decode(args[2]); // Final value
+secs = Integer.decode(args[3]); // Wait between changes
+while(curr <= end) {
setprop("throughput",curr.toString()); // Needs to be a string here
Thread.sleep(secs*1000);
curr += inc;
}
printprop("throughput");
</pre>
-<p>The script can be stored in a file (throughput.bsh, say), and sent to the server using bshclient.jar.
+<p>The script can be stored in a file (<span class="code">throughput.bsh</span>, say), and sent to the server using <span class="code">bshclient.jar</span>.
For example:
</p>
-<pre>
+<pre class="source">
java -jar ../lib/bshclient.jar localhost 9000 throughput.bsh 70 5 100 60
</pre>
-</div><div class="section"><h1 id="bsh_scripting">16.9 BeanShell scripting<a class="sectionlink" href="#bsh_scripting" title="Link to here">¶</a></h1>
-<div class="subsection"><h2>16.9.1 Overview<a class="sectionlink" href="#bsh_overview" title="Link to here">¶</a></h2>
+</div><div class="section"><h1 id="bsh_scripting">18.9 BeanShell scripting<a class="sectionlink" href="#bsh_scripting" title="Link to here">¶</a></h1>
+<div class="subsection"><h2 id="bsh_overview">18.9.1 Overview<a class="sectionlink" href="#bsh_overview" title="Link to here">¶</a></h2>
<p>
Each BeanShell test element has its own copy of the interpreter (for each thread).
If the test element is repeatedly called, e.g. within a loop, then the interpreter is retained
-between invocations unless the "Reset bsh.Interpreter before each call" option is selected.
-For intensive load testing, it is recommended to use a JSR223 scripting language whose ScriptingEngine implements Compilable,
+between invocations unless the "<span class="code">Reset bsh.Interpreter before each call</span>" option is selected.
+For intensive load testing, it is recommended to use a JSR223 scripting language whose ScriptingEngine implements <span class="code">Compilable</span>,
see JSR223 section below for more details.
</p>
<p>
@@ -247,54 +246,58 @@ Some long-running tests may cause the in
</p>
<p>
You can test BeanShell scripts outside JMeter by using the command-line interpreter:
-<pre>
-$ java -cp bsh-xxx.jar[;other jars as needed] bsh.Interperter file.bsh [parameters]
+<pre class="source">
+$ java -cp bsh-xxx.jar[;other jars as needed] bsh.Interpreter file.bsh [parameters]
+</pre>
or
-$ java -cp bsh-xxx.jar bsh.Interperter
+<pre class="source">
+$ java -cp bsh-xxx.jar bsh.Interpreter
bsh% source("file.bsh");
bsh% exit(); // or use EOF key (e.g. ^Z or ^D)
</pre>
</p>
</div>
-<div class="subsection"><h2>16.9.2 Sharing Variables<a class="sectionlink" href="#bsh_variables" title="Link to here">¶</a></h2>
+<div class="subsection"><h2 id="bsh_variables">18.9.2 Sharing Variables<a class="sectionlink" href="#bsh_variables" title="Link to here">¶</a></h2>
<p>
Variables can be defined in startup (initialisation) scripts.
-These will be retained across invocations of the test element, unless the reset option is used.\
+These will be retained across invocations of the test element, unless the reset option is used.
</p>
<p>
-Scripts can also access JMeter variables using the get() and put() methods of the "vars" variable,
-for example: <span class="code">vars.get("HOST"); vars.put("MSG","Successful");</span>.
-The get() and put() methods only support variables with String values,
-but there are also getObject() and putObject() methods which can be used for arbitrary objects.
+Scripts can also access JMeter variables using the <span class="code">get()</span> and <span class="code">put()</span> methods of the "<span class="code">vars</span>" variable,
+for example:
+<pre class="source">vars.get("HOST");
+vars.put("MSG","Successful");</pre>
+The <span class="code">get()</span> and <span class="code">put()</span> methods only support variables with String values,
+but there are also <span class="code">getObject()</span> and <span class="code">putObject()</span> methods which can be used for arbitrary objects.
JMeter variables are local to a thread, but can be used by all test elements (not just Beanshell).
</p>
<p>
If you need to share variables between threads, then JMeter properties can be used:
-<pre>
+<pre class="source">
import org.apache.jmeter.util.JMeterUtils;
-String value=JMeterUtils.getPropDefault("name","");
+String value = JMeterUtils.getPropDefault("name","");
JMeterUtils.setProperty("name", "value");
</pre>
-The sample .bshrc files contain sample definitions of getprop() and setprop() methods.
+The sample <span class="code">.bshrc</span> files contain sample definitions of <span class="code">getprop()</span> and <span class="code">setprop()</span> methods.
</p>
<p>
-Another possible method of sharing variables is to use the "bsh.shared" shared namespace.
+Another possible method of sharing variables is to use the "<span class="code">bsh.shared</span>" shared namespace.
For example:
-<pre>
+<pre class="source">
if (bsh.shared.myObj == void){
// not yet defined, so create it:
- myObj=new AnyObject();
+ myObj = new AnyObject();
}
bsh.shared.myObj.process();
</pre>
Rather than creating the object in the test element, it can be created in the startup file
-defined by the JMeter property "beanshell.init.file". This is only processed once.
+defined by the JMeter property "<span class="code">beanshell.init.file</span>". This is only processed once.
</p>
</div>
-</div><div class="section"><h1 id="developing_scripts">16.10 Developing script functions in BeanShell, Javascript or Jexl etc.<a class="sectionlink" href="#developing_scripts" title="Link to here">¶</a></h1>
+</div><div class="section"><h1 id="developing_scripts">18.10 Developing script functions in BeanShell, Javascript or Jexl etc.<a class="sectionlink" href="#developing_scripts" title="Link to here">¶</a></h1>
<p>
It's quite hard to write and test scripts as functions.
-However, JMeter has the JSR223, BSF (and BeanShell) samplers which can be used instead.
+However, JMeter has the JSR223, BSF (and BeanShell) samplers which can be used instead.
</p>
<p>
Create a simple Test Plan containing the JSR223 or BSF Sampler and Tree View Listener.
@@ -305,50 +308,50 @@ Also the result of running the script wi
<p>
Once the script is working properly, it can be stored as a variable on the Test Plan.
The script variable can then be used to create the function call.
-For example, suppose a BeanShell script is stored in the variable RANDOM_NAME.
+For example, suppose a BeanShell script is stored in the variable <span class="code">RANDOM_NAME</span>.
The function call can then be coded as <span class="code">${__BeanShell(${RANDOM_NAME})}</span>.
-There is no need to escape any commas in the script,
+There is no need to escape any commas in the script,
because the function call is parsed before the variable's value is interpolated.
</p>
-</div><div class="section"><h1 id="parameterising_tests">16.11 Parameterising tests<a class="sectionlink" href="#parameterising_tests" title="Link to here">¶</a></h1>
+</div><div class="section"><h1 id="parameterising_tests">18.11 Parameterising tests<a class="sectionlink" href="#parameterising_tests" title="Link to here">¶</a></h1>
<p>
Often it is useful to be able to re-run the same test with different settings.
For example, changing the number of threads or loops, or changing a hostname.
</p>
<p>
One way to do this is to define a set of variables on the Test Plan, and then use those variables in the test elements.
-For example, one could define the variable LOOPS=10, and refer to that in the Thread Group as ${LOOPS}.
-To run the test with 20 loops, just change the value of the LOOPS variable on the Test Plan.
+For example, one could define the variable <span class="code">LOOPS=10</span>, and refer to that in the Thread Group as <span class="code">${LOOPS}</span>.
+To run the test with 20 loops, just change the value of the <span class="code">LOOPS</span> variable on the Test Plan.
</p>
<p>
This quickly becomes tedious if you want to run lots of tests in non-GUI mode.
One solution to this is to define the Test Plan variable in terms of a property,
for example <span class="code">LOOPS=${__P(loops,10))}</span>.
-This uses the value of the property "loops", defaulting to 10 if the property is not found.
-The "loops" property can then be defined on the JMeter command-line:
-<span class="code">jmeter ... -Jloops=12 ...</span>.
-If there are a lot of properties that need to be changed together,
+This uses the value of the property "<span class="code">loops</span>", defaulting to <span class="code">10</span> if the property is not found.
+The "<span class="code">loops</span>" property can then be defined on the JMeter command-line:
+<pre class="source">jmeter … -Jloops=12 …</pre>
+If there are a lot of properties that need to be changed together,
then one way to achieve this is to use a set of property files.
-The appropriate property file can be passed in to JMeter using the -q command-line option.
+The appropriate property file can be passed in to JMeter using the <span class="code">-q</span> command-line option.
</p>
-</div><div class="section"><h1 id="jsr223">16.12 JSR223 Elements<a class="sectionlink" href="#jsr223" title="Link to here">¶</a></h1>
+</div><div class="section"><h1 id="jsr223">18.12 JSR223 Elements<a class="sectionlink" href="#jsr223" title="Link to here">¶</a></h1>
<p>
-For intensive load testing, the recommended scripting language is one whose ScriptingEngine implements the Compilable interface.
-Groovy scripting engine implements Compilable. However neither Beanshell nor Javascript do so as of release date of JMeter 2.13, so it is
-recommended to avoid them for intensive load testing.
-[Note: Beanshell implements the Compilable interface but it has not been coded - the method just throws an Exception.
-JMeter has an explicit work-round for this bug.]
+For intensive load testing, the recommended scripting language is one whose ScriptingEngine implements the <span class="code">Compilable</span> interface.
+Groovy scripting engine implements <span class="code">Compilable</span>. However neither Beanshell nor Javascript do so as of release date of JMeter 2.13, so it is
+recommended to avoid them for intensive load testing.
+<div class="clear"></div><div class="note">Note: Beanshell implements the <span class="code">Compilable</span> interface but it has not been coded - the method just throws an Exception.
+JMeter has an explicit work-round for this bug.</div><div class="clear"></div>
When using JSR 223 elements, always set caching key to a unique value to ensure the script compilation is cached if underlying language supports it.
-Ensure the script does not use any variable using ${varName} as caching would take only first value of ${varName}. Instead use :
-<span class="code">
+Ensure the script does not use any variable using <span class="code">${varName}</span> as caching would take only first value of <span class="code">${varName}</span>. Instead use :
+<pre class="source">
vars.get("varName")
-</span>
+</pre>
</p>
<p>
You can also pass them as Parameters to the script and use them this way.
</p>
-</div><div class="section"><h1 id="sharing_variables">16.13 Sharing variables between threads and thread groups<a class="sectionlink" href="#sharing_variables" title="Link to here">¶</a></h1>
+</div><div class="section"><h1 id="sharing_variables">18.13 Sharing variables between threads and thread groups<a class="sectionlink" href="#sharing_variables" title="Link to here">¶</a></h1>
<p>
Variables are local to a thread; a variable set in one thread cannot be read in another.
This is by design. For variables that can be determined before a test starts, see
@@ -357,19 +360,27 @@ If the value is not known until the test
<ul>
<li>Store the variable as a property - properties are global to the JMeter instance</li>
<li>Write variables to a file and re-read them.</li>
-<li>Use the bsh.shared namespace - see <a href="#bsh_variables">above</a></li>
+<li>Use the <span class="code">bsh.shared</span> namespace - see <a href="#bsh_variables">above</a></li>
<li>Write your own Java classes</li>
</ul>
</p>
-</div><div class="section"><h1 id="properties">16.14 Managing properties<a class="sectionlink" href="#properties" title="Link to here">¶</a></h1>
-<p>When you need to modify jmeter properties, ensure you don't modify jmeter.properties file, <b>instead copy the property from jmeter.properties and modify its value in user.properties file</b>.<br>
+</div><div class="section"><h1 id="properties">18.14 Managing properties<a class="sectionlink" href="#properties" title="Link to here">¶</a></h1>
+<p>When you need to modify jmeter properties, ensure you don't modify <span class="code">jmeter.properties</span> file,
+<b>instead copy the property from <span class="code">jmeter.properties</span> and modify its value in <span class="code">user.properties</span> file</b>.<br>
Doing so will ease you migration to the next version of JMeter. <br>
-Note that in the documentation jmeter.properties is frequently mentioned but this should be understood as "Copy from jmeter.properties to user.properties the property you want to modify and do so in the latter file".</p>
-<div class="clear"></div><div class="note">user.properties file superseeds the properties defined in jmeter.properties</div><div class="clear"></div>
-</div><ul class="pagelinks"><li><a href="remote-test.html">< Prev</a></li><li><a href="../index.html">Index</a></li><li><a href="boss.html">Next ></a></li></ul></div><div class="footer"><div class="copyright">
+Note that in the documentation <span class="code">jmeter.properties</span> is frequently mentioned but this should be understood as
+"Copy from <span class="code">jmeter.properties</span> to <span class="code">user.properties</span> the property you want to modify and do so in the latter file".</p>
+<div class="clear"></div><div class="note"><span class="code">user.properties</span> file supersedes the properties defined in <span class="code">jmeter.properties</span></div><div class="clear"></div>
+</div><div class="section"><h1 id="deprecation">18.15 Deprecated elements<a class="sectionlink" href="#deprecation" title="Link to here">¶</a></h1>
+<p>It is advised not to use deprecated elements (marked as such in <a href="../changes.html">changes list</a> and in <a href="./component_reference.html">component reference</a>)
+and to migrate to new advised elements if available or new way of doing the same thing. <br>
+Deprecated elements are removed from the menu in version N but can be enabled for migration by modifying <span class="code">not_in_menu</span> property in <span class="code">user.properties</span> file and removing the full class name
+of the element from there.<br></p>
+<div class="clear"></div><div class="note">Please note that deprecated elements in version N will be removed definitely in version N+1, so ensure you stop using them as soon as possible.</div><div class="clear"></div>
+</div><ul class="pagelinks"><li><a href="realtime-results.html">< Prev</a></li><li><a href="../index.html">Index</a></li><li><a href="boss.html">Next ></a></li></ul></div><div class="footer"><div class="copyright">
Copyright ©
1999 –
- 2015
+ 2016
, Apache Software Foundation
</div><div class="trademarks">Apache, Apache JMeter, JMeter, the Apache
feather, and the Apache JMeter logo are
Modified: jmeter/trunk/docs/usermanual/boss.html
URL: http://svn.apache.org/viewvc/jmeter/trunk/docs/usermanual/boss.html?rev=1739469&r1=1739468&r2=1739469&view=diff
==============================================================================
--- jmeter/trunk/docs/usermanual/boss.html (original)
+++ jmeter/trunk/docs/usermanual/boss.html Sat Apr 16 14:36:00 2016
@@ -1,23 +1,12 @@
<!DOCTYPE html SYSTEM "about:legacy-compat">
<html lang="en"><head><META http-equiv="Content-Type" content="text/html; charset=iso-8859-15"><title>Apache JMeter
-
- User's Manual: My boss wants me to...</title><meta name="author" value="Martin Ramshaw"><meta name="email" value="mramshaw at alumni.concordia.ca"><meta name="author" value="Philippe Mouawad"><meta name="email" value="p.mouawad at ubik-ingenierie.com"><meta name="viewport" content="width=device-width, initial-scale=1"><link href="http://fonts.googleapis.com/css?family=Merriweather:400normal" rel="stylesheet" type="text/css"><link rel="stylesheet" type="text/css" href="../css/new-style.css"></head><body role="document"><a href="#content" class="hidden">Main content</a><div class="header"><!--
+ User's Manual: My boss wants me to …</title><meta name="author" value="JMeter developers"><meta name="email" value="dev@jmeter.apache.org"><meta name="viewport" content="width=device-width, initial-scale=1"><link href="http://fonts.googleapis.com/css?family=Merriweather:400normal" rel="stylesheet" type="text/css"><link rel="stylesheet" type="text/css" href="../css/new-style.css"><link rel="apple-touch-icon-precomposed" href="../images/apple-touch-icon.png"><link rel="icon" href="../images/favicon.png"><meta name="msapplication-TileColor" content="#ffffff"><meta name="msapplication-TileImage" content="../images/mstile-144x144.png"><meta name="theme-color" content="#ffffff"></head><body role="document"><a href="#content" class="hidden">Main content</a><div class="header"><!--
APACHE LOGO
- --><div><a href="http://www.apache.org"><img title="Apache Software Foundation" width="290" height="75" src="../images/asf-logo.png" alt="Logo ASF"></a></div><!--
+ --><div><a href="http://www.apache.org"><img title="Apache Software Foundation" class="logo" src="../images/asf-logo.svg" alt="Logo ASF"></a></div><!--
PROJECT LOGO
- --><div><a href="http://jmeter.apache.org/"><img src="../images/logo.jpg" alt="Apache JMeter"></a></div><div class="twitter"><div><a href="https://twitter.com/share" class="twitter-share-button" data-text="Powerful Load Testing with Apache #JMeter" data-via="ApacheJMeter" data-lang="en-gb" data-size="large">Tweet</a><script>
- (function(d,s,id){
- var js,
- fjs=d.getElementsByTagName(s)[0],
- p=/^http:/.test(d.location)?'http':'https';
- if (!d.getElementById(id)) {
- js=d.createElement(s);
- js.id=id;
- js.src=p+'://platform.twitter.com/widgets.js';
- fjs.parentNode.insertBefore(js,fjs);
- }
- })(document, 'script', 'twitter-wjs');
- </script></div><div><a href="https://twitter.com/ApacheJMeter" class="twitter-follow-button" data-show-count="false" data-lang="en-gb" data-size="large">Follow</a><script>(function(d,s,id){
+ --><div><a href="http://jmeter.apache.org/"><img class="logo" src="../images/logo.svg" alt="Apache JMeter"></a></div><div class="banner"><iframe src="http://www.apache.org/ads/bannerbar.html" style="border-width:0;" frameborder="0" scrolling="no"></iframe><div class="clear"></div></div></div><div class="nav"><div class="social menu"><div><a href="https://twitter.com/share" class="twitter-share-button" data-text="Powerful Load Testing with Apache #JMeter" data-via="ApacheJMeter" data-lang="en-gb" data-size="large">Tweet</a><script>
+ (function(d,s,id){
var js,
fjs=d.getElementsByTagName(s)[0],
p=/^http:/.test(d.location)?'http':'https';
@@ -27,45 +16,56 @@
js.src=p+'://platform.twitter.com/widgets.js';
fjs.parentNode.insertBefore(js,fjs);
}
- })(document, 'script', 'twitter-wjs');
- </script></div></div><div class="banner"><iframe src="http://www.apache.org/ads/bannerbar.html" style="border-width:0;" frameborder="0" scrolling="no"></iframe><div class="clear"></div></div></div><div class="nav"><ul class="menu"><li><div class="menu-title">About</div><ul><li><a href="../index.html">Overview</a></li><li><a href="http://twitter.com/ApacheJMeter">JMeter on Twitter<img src="../images/twitter.png" alt="Icon for JMeter on Twitter"></a></li><li><a href="../issues.html">Issue Tracking</a></li><li><a href="http://projects.apache.org/feeds/rss/jmeter.xml">Subscribe to What's New</a></li><li><a href="http://www.apache.org/licenses/">License</a></li></ul></li></ul><ul class="menu"><li><div class="menu-title">Download</div><ul><li><a href="../download_jmeter.cgi">Download Releases</a></li><li><a href="../nightly.html">Developer (Nightly) Builds</a></li></ul></li></ul><ul class="menu"><li><div class="menu-title">Documentation</div><ul><li><a href="../changes.html"
>Changes per version</a></li><li><a href="../usermanual/get-started.html">Get Started</a></li><li><a href="../usermanual/index.html">User Manual</a></li><li><a href="../usermanual/best-practices.html">Best Practices</a></li><li><a href="../usermanual/component_reference.html">Component Reference</a></li><li><a href="../usermanual/functions.html">Functions Reference</a></li><li><a href="../api/index.html">Javadocs</a></li><li><a href="../building.html">Building JMeter and Add-Ons</a></li><li><a href="http://wiki.apache.org/jmeter">JMeter Wiki</a></li><li><a href="http://wiki.apache.org/jmeter/JMeterFAQ">FAQ (Wiki)</a></li></ul></li></ul><ul class="menu"><li><div class="menu-title">Tutorials (PDF format)</div><ul><li><a href="../usermanual/jmeter_distributed_testing_step_by_step.pdf">Distributed Testing</a></li><li><a href="../usermanual/jmeter_proxy_step_by_step.pdf">Recording Tests</a></li><li><a href="../usermanual/junitsampler_tutorial.pdf">JUnit Sampler</a></li><li><a href="../us
ermanual/jmeter_accesslog_sampler_step_by_step.pdf">Access Log Sampler</a></li><li><a href="../extending/jmeter_tutorial.pdf">Extending JMeter</a></li></ul></li></ul><ul class="menu"><li><div class="menu-title">Community</div><ul><li><a href="http://wiki.apache.org/jmeter/JMeterCommitters">Contributors</a></li><li><a href="../mail.html">Mailing Lists</a></li><li><a href="../svnindex.html">SVN Repositories</a></li></ul></li></ul><ul class="menu"><li><div class="menu-title">Foundation</div><ul><li><a href="http://www.apache.org/">ASF</a></li><li><a href="http://www.apache.org/foundation/getinvolved.html">Get Involved in the ASF</a></li><li><a href="http://www.apache.org/foundation/sponsorship.html">Sponsorship</a></li><li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li></ul></li></ul></div><div class="main" id="content"><ul class="pagelinks"><li><a href="best-practices.html">< Prev</a></li><li><a href="../index.html">Index</a></li><li><a href="component_refere
nce.html">Next ></a></li></ul><div class="section"><h1 id="boss">17. Help! My boss wants me to load test our application!<a class="sectionlink" href="#boss" title="Link to here">¶</a></h1>
+ })(document, 'script', 'twitter-wjs');
+ </script></div><div><a href="https://twitter.com/ApacheJMeter" class="twitter-follow-button" data-show-count="false" data-lang="en-gb" data-size="large">Follow</a><script>(function(d,s,id){
+ var js,
+ fjs=d.getElementsByTagName(s)[0],
+ p=/^http:/.test(d.location)?'http':'https';
+ if (!d.getElementById(id)) {
+ js=d.createElement(s);
+ js.id=id;
+ js.src=p+'://platform.twitter.com/widgets.js';
+ fjs.parentNode.insertBefore(js,fjs);
+ }
+ })(document, 'script', 'twitter-wjs');
+ </script></div><div><a href="https://github.com/apache/jmeter"><img alt="star this repo" src="http://githubbadges.com/star.svg?user=apache&repo=jmeter&style=default"></a></div><div><a href="https://github.com/apache/jmeter/fork"><img alt="fork this repo" src="http://githubbadges.com/fork.svg?user=apache&repo=jmeter&style=default"></a></div><div><a href="https://maven-badges.herokuapp.com/maven-central/org.apache.jmeter/ApacheJMeter"><img alt="Maven Central" src="https://maven-badges.herokuapp.com/maven-central/org.apache.jmeter/ApacheJMeter/badge.png"></a></div></div><ul class="menu"><li onClick="return true"><div class="menu-title">About</div><ul><li><a href="../index.html">Overview</a></li><li><a href="http://www.apache.org/licenses/">License</a></li></ul></li></ul><ul class="menu"><li onClick="return true"><div class="menu-title">Download</div><ul><li><a href="../download_jmeter.cgi">Download Releases</a></li><li><a href="../nightly.html">Developer
(Nightly) Builds</a></li></ul></li></ul><ul class="menu"><li onClick="return true"><div class="menu-title">Documentation</div><ul><li><a href="../changes.html">Changes per version</a></li><li><a href="../usermanual/get-started.html">Get Started</a></li><li><a href="../usermanual/index.html">User Manual</a></li><li><a href="../usermanual/best-practices.html">Best Practices</a></li><li><a href="../usermanual/component_reference.html">Component Reference</a></li><li><a href="../usermanual/functions.html">Functions Reference</a></li><li><a href="../api/index.html">Javadocs</a></li><li><a href="../building.html">Building JMeter and Add-Ons</a></li><li><a href="http://wiki.apache.org/jmeter">JMeter Wiki</a></li><li><a href="http://wiki.apache.org/jmeter/JMeterFAQ">FAQ (Wiki)</a></li></ul></li></ul><ul class="menu"><li onClick="return true"><div class="menu-title">Tutorials (PDF format)</div><ul><li><a href="../usermanual/jmeter_distributed_testing_step_by_step.pdf">Distributed Testing</a
></li><li><a href="../usermanual/jmeter_proxy_step_by_step.pdf">Recording Tests</a></li><li><a href="../usermanual/junitsampler_tutorial.pdf">JUnit Sampler</a></li><li><a href="../usermanual/jmeter_accesslog_sampler_step_by_step.pdf">Access Log Sampler</a></li><li><a href="../extending/jmeter_tutorial.pdf">Extending JMeter</a></li></ul></li></ul><ul class="menu"><li onClick="return true"><div class="menu-title">Community</div><ul><li><a href="../issues.html">Issue Tracking</a></li><li><a href="../mail.html">Mailing Lists</a></li><li><a href="../svnindex.html">Source Repositories</a></li><li><a href="../building.html">Building and Contributing</a></li><li><a href="https://projects.apache.org/project.html?jmeter">Project info at Apache</a></li><li><a href="http://wiki.apache.org/jmeter/JMeterCommitters">Contributors</a></li></ul></li></ul><ul class="menu"><li onClick="return true"><div class="menu-title">Foundation</div><ul><li><a href="http://www.apache.org/">ASF</a></li><li><a href=
"http://www.apache.org/foundation/getinvolved.html">Get Involved in the ASF</a></li><li><a href="http://www.apache.org/foundation/sponsorship.html">Sponsorship</a></li><li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li></ul></li></ul></div><div class="main" id="content"><ul class="pagelinks"><li><a href="best-practices.html">< Prev</a></li><li><a href="../index.html">Index</a></li><li><a href="component_reference.html">Next ></a></li></ul><div class="section"><h1 id="boss">19. Help! My boss wants me to load test our application!<a class="sectionlink" href="#boss" title="Link to here">¶</a></h1>
<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>
-<div class="subsection"><h2>17.1 Questions to ask<a class="sectionlink" href="#questions" title="Link to here">¶</a></h2>
-<p>What is our anticipated average number of users (normal load) ?
+<div class="subsection"><h2 id="questions">19.1 Questions to ask<a class="sectionlink" href="#questions" title="Link to here">¶</a></h2>
+<p>What is our anticipated average number of users (normal load)?
</p>
-<p>What is our anticipated peak number of users ?
+<p>What is our anticipated peak number of users?
</p>
<p>When is a good time to load-test our application (i.e. off-hours or week-ends),
-bearing in mind that this may very well crash one or more of our servers ?
+bearing in mind that this may very well crash one or more of our servers?
</p>
-<p>Does our application have state ? If so, how does our application manage it
-(cookies, session-rewriting, or some other method) ?
+<p>Does our application have state? If so, how does our application manage it
+(cookies, session-rewriting, or some other method)?
</p>
<p>What is the testing intended to achieve?</p>
</div>
-<div class="subsection"><h2>17.2 Resources<a class="sectionlink" href="#resources" title="Link to here">¶</a></h2>
+<div class="subsection"><h2 id="resources">19.2 Resources<a class="sectionlink" href="#resources" title="Link to here">¶</a></h2>
<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>
- <div class="subsection"><h2>17.2.1 Network<a class="sectionlink" href="#network" title="Link to here">¶</a></h2>
- <p>Who knows our network topology ? If you run into any firewall or
+ <div class="subsection"><h2 id="network">19.2.1 Network<a class="sectionlink" href="#network" title="Link to here">¶</a></h2>
+ <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)
would be a very nice thing. Knowing who can set one up for you
(if you feel that this is necessary) will be very useful. If the
application doesn't scale as expected, who can add additional
- hardware ?
+ hardware?
</p>
</div>
- <div class="subsection"><h2>17.2.2 Application<a class="sectionlink" href="#application" title="Link to here">¶</a></h2>
- <p>Who knows how our application functions ? The normal sequence is
+ <div class="subsection"><h2 id="application">19.2.2 Application<a class="sectionlink" href="#application" title="Link to here">¶</a></h2>
+ <p>Who knows how our application functions? The normal sequence is
<ul>
<li>test (low-volume - can we benchmark our application?)</li>
<li>benchmark (the average number of users)</li>
@@ -80,7 +80,7 @@ people are, so that you can ask them for
during this process, so be prepared to defend your work.</p>
</div>
</div>
-<div class="subsection"><h2>17.3 What platform should I use to run the benchmarks/load-tests ?<a class="sectionlink" href="#platform" title="Link to here">¶</a></h2>
+<div class="subsection"><h2 id="platform">19.3 What platform should I use to run the benchmarks/load-tests?<a class="sectionlink" href="#platform" title="Link to here">¶</a></h2>
<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.
@@ -95,10 +95,16 @@ you have a little more money, there are
This may be worth it if you need the support.
</p>
<p>
-For non-Windows platforms, investigate "ulimit -n unlimited" with a view to
-including it in your user account startup scripts (.bashrc or .cshrc scripts
+For non-Windows platforms, investigate "<span class="code">ulimit -n unlimited</span>" with a view to
+including it in your user account startup scripts (<span class="code">.bashrc</span> or <span class="code">.cshrc</span> scripts
for the testing account).
</p>
+<p>
+Also note that some Linux/Unix editions are intended for server use.
+These generally have minimal or no GUI support.
+Such OSes should be OK for running JMeter in non-GUI mode, but JMeter GUI mode probably won't work
+unless you install a minimal GUI environment.
+</p>
<p>As you progress to larger-scale benchmarks/load-tests, this platform
will become the limiting factor. So it's worth using the best hardware and
software that you have available. Remember to include the hardware/software
@@ -118,30 +124,30 @@ The batch log file can then be loaded in
use CSV output and import the data into a spreadsheet.</p>
<div class="clear"></div><div class="note">Remember GUI mode is for Script creation and debugging, not for load testing</div><div class="clear"></div>
</div>
-<div class="subsection"><h2>17.4 Tools<a class="sectionlink" href="#tools" title="Link to here">¶</a></h2>
+<div class="subsection"><h2 id="tools">19.4 Tools<a class="sectionlink" href="#tools" title="Link to here">¶</a></h2>
<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>
- <div class="subsection"><h2>17.4.1 ping<a class="sectionlink" href="#ping" title="Link to here">¶</a></h2>
+ <div class="subsection"><h2 id="ping">19.4.1 ping<a class="sectionlink" href="#ping" title="Link to here">¶</a></h2>
<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'.
+ target site. Options can be specified so that '<span class="code">ping</span>' provides the
+ same type of route reporting as '<span class="code">traceroute</span>'.
</p>
</div>
- <div class="subsection"><h2>17.4.2 nslookup/dig<a class="sectionlink" href="#dig" title="Link to here">¶</a></h2>
+ <div class="subsection"><h2 id="dig">19.4.2 nslookup/dig<a class="sectionlink" href="#dig" title="Link to here">¶</a></h2>
<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
+ While the <b>user</b> will normally use a human-readable internet
+ address, <b>you</b> may wish to avoid the overhead of DNS lookups when
performing benchmarking/load-testing. These can be used to determine
the unique address (dotted quad) of your target site.
</p>
</div>
- <div class="subsection"><h2>17.4.3 traceroute<a class="sectionlink" href="#traceroute" title="Link to here">¶</a></h2>
+ <div class="subsection"><h2 id="traceroute">19.4.3 traceroute<a class="sectionlink" href="#traceroute" title="Link to here">¶</a></h2>
<p>
- If you cannot "ping" your target site, this may be used to determine
+ If you cannot "<span class="code">ping</span>" your target site, this may be used to determine
the problem (possibly a firewall or a proxy). It can also be used
to estimate the overall network latency (running locally should give
the lowest possible network latency - remember that your users will
@@ -150,37 +156,21 @@ and any supplied documentation).
</p>
</div>
</div>
-<div class="subsection"><h2>17.5 How can I enhance JMeter ?<a class="sectionlink" href="#plugins" title="Link to here">¶</a></h2>
-<p>There a lot of open-source and commercial plugins that can enhance JMeter, let's mention here the main open-source ones:
+<div class="subsection"><h2 id="plugins">19.5 How can I enhance JMeter?<a class="sectionlink" href="#plugins" title="Link to here">¶</a></h2>
+<p>There a lot of open-source and commercial providers who provide JMeter plugins or other resources for use with JMeter.
+Some of these are listed on the JMeter Wiki.
+They are listed under several categories:
+<ul>
+<li><a href="http://wiki.apache.org/jmeter/JMeterPlugins">JMeterPlugins</a> - plugins for extending JMeter</li>
+<li><a href="http://wiki.apache.org/jmeter/JMeterAddons">JMeterAddons</a> - addons for use with JMeter, e.g. plugins for browsers, Maven and Jenkins.</li>
+<li><a href="http://wiki.apache.org/jmeter/JMeterServices">JMeterServices</a> - 3rd party services, e.g. cloud-based JMeter</li>
+</ul>
+Note that appearance of these on the Wiki does not imply any endorsement by the Apache JMeter project.
+Any requests for support should be directed to the relevant supplier.
</p>
- <div class="subsection"><h2>17.5.1 JMeter-Plugins<a class="sectionlink" href="#jmeter-plugins" title="Link to here">¶</a></h2>
- <p>This <a href="http://jmeter-plugins.org/" target="_blank">non official project</a> is THE companion to core JMeter.<br>
- It provides many useful extensions, among which:
- <ul>
- <li>Active Threads Over Time Graph Listener</li>
- <li>Response Times vs Threads Graph Listener</li>
- <li>Transaction Throughput vs Threads Graph Listener</li>
- <li>GraphGenerator listener to create graphs at end of a load test</li>
- <li>Selenium WebDriver Sampler</li>
- <li>....</li>
- </ul>
- </p>
- </div>
- <div class="subsection"><h2>17.5.2 JMeter Plugin for Maven<a class="sectionlink" href="#jmeter-maven-plugin" title="Link to here">¶</a></h2>
- <p>This <a href="http://jmeter.lazerycode.com/" target="_blank">non official plugin</a> allows you to run your automated JMeter tests through Maven.</p>
- </div>
- <div class="subsection"><h2>17.5.3 JMeter Performance Plugin<a class="sectionlink" href="#jmeter-performance-plugin" title="Link to here">¶</a></h2>
- <p>This <a href="https://wiki.jenkins-ci.org/display/JENKINS/Performance+Plugin" target="_blank">non official plugin</a> allows you to capture reports from JMeter and JUnit.<br>
- Jenkins will generate graphic charts with the trend report of performance and robustness.
- It includes the feature of setting the final build status as good, unstable or failed, based on the reported error percentage.
- </p>
- </div>
- <div class="subsection"><h2>17.5.4 JMeter plugin for AWS<a class="sectionlink" href="#jmeter-ec2" title="Link to here">¶</a></h2>
- <p>This <a href="https://github.com/oliverlloyd/jmeter-ec2" target="_blank">non official plugin</a> automates running Apache JMeter on Amazon EC2</p>
- </div>
</div>
-<div class="subsection"><h2>17.6 Why Java ?<a class="sectionlink" href="#java" title="Link to here">¶</a></h2>
-<p>Why not Perl or C ?
+<div class="subsection"><h2 id="java">19.6 Why Java?<a class="sectionlink" href="#java" title="Link to here">¶</a></h2>
+<p>Why not Perl or C?
</p>
<p>Well, Perl might be a very good choice except that the Benchmark package
seems to give fairly fuzzy results. Also, simulating multiple users with
@@ -190,7 +180,7 @@ be processes). However, the Perl communi
someone has already written something that seems useful, this could be a very
good solution.
</p>
-<p>C, of course, is a very good choice (check out the Apache <b>ab</b> tool).
+<p>C, of course, is a very good choice (check out the Apache <span class="code">ab</span> tool).
But be prepared to write all of the custom networking, threading, and state
management code that you will need to benchmark your application.
</p>
@@ -204,7 +194,7 @@ garbage-collection, and byte-code level
</div><ul class="pagelinks"><li><a href="best-practices.html">< Prev</a></li><li><a href="../index.html">Index</a></li><li><a href="component_reference.html">Next ></a></li></ul></div><div class="footer"><div class="copyright">
Copyright ©
1999 –
- 2015
+ 2016
, Apache Software Foundation
</div><div class="trademarks">Apache, Apache JMeter, JMeter, the Apache
feather, and the Apache JMeter logo are