-
Notifications
You must be signed in to change notification settings - Fork 0
/
index.html
116 lines (99 loc) · 5.88 KB
/
index.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
<ol class="breadcrumb">
<li><a href="#">Gatling documentation</a></li>
<li><a href="">
Gatling
</a></li>
</ol>
<div class="content-left-wrap col-md-9">
<div id="primary" class="content-area">
<main itemscope="" itemtype="http://schema.org/WebPageElement" itemprop="mainContentOfPage" id="main"
class="site-main">
<article id="documentation" class="type-post status-publish format-standard hentry category-non-classe">
<header class="entry-header">
<h1 class="entry-title" itemprop="headline">Gatling</h1>
</header>
<div class="entry-content" itemprop="text">
<div class="section" id="gatling">
<p>Gatling is a highly capable load testing tool.
It is designed for ease of use, maintainability and high performance.</p>
<p>Out of the box, Gatling comes with excellent support of the HTTP protocol that makes it a tool of choice for load testing any HTTP server.
As the core engine is actually protocol agnostic, it is perfectly possible to implement support for other protocols.
For example, Gatling currently also ships JMS support.</p>
<p>The <a class="reference internal" href="quickstart.html#quickstart"><span class="std std-ref">Quickstart</span></a> has an overview of the most important concepts, walking you through the setup of a simple scenario for load testing an HTTP server.</p>
<p>Having <em>scenarios</em> that are defined in code and are resource efficient are the two requirements that motivated us to create Gatling. Based on an expressive <a class="reference external" href="http://en.wikipedia.org/wiki/Domain-specific_language">DSL</a>, the <em>scenarios</em> are self explanatory. They are easy to maintain and can be kept in a version control system.</p>
<p>Gatling’s architecture is asynchronous as long as the underlying protocol, such as HTTP, can be implemented in a non blocking way. This kind of architecture lets us implement virtual users as messages instead of dedicated threads, making them very resource cheap. Thus, running thousands of concurrent virtual users is not an issue.</p>
<div class="section" id="migrating-from-a-previous-version-of-gatling">
<h2>Migrating from a previous version of Gatling<a class="headerlink" href="#migrating-from-a-previous-version-of-gatling" title="Permalink to this headline">¶</a></h2>
<ul class="simple">
<li>If you’re migrating from Gatling 2.1 to Gatling 2.2, please consult the <a class="reference internal" href="migration_guides/2.1-to-2.2.html#to-2-2"><span class="std std-ref">dedicated migration guide</span></a>.</li>
<li>Otherwise, please follow the <a class="reference internal" href="migration_guides/index.html#migration-guides"><span class="std std-ref">previous migration guides</span></a>.</li>
</ul>
</div>
<div class="section" id="user-s-guide">
<h2>User’s guide<a class="headerlink" href="#user-s-guide" title="Permalink to this headline">¶</a></h2>
<div class="toctree-wrapper compound">
<ul>
<li class="toctree-l1"><a class="reference internal" href="whats_new/index.html">Migration guides</a></li>
<li class="toctree-l1"><a class="reference internal" href="migration_guides/index.html">Migration guides</a></li>
<li class="toctree-l1"><a class="reference internal" href="quickstart.html">Quickstart</a></li>
<li class="toctree-l1"><a class="reference internal" href="advanced_tutorial.html">Advanced Tutorial</a></li>
<li class="toctree-l1"><a class="reference internal" href="general/index.html">General</a></li>
<li class="toctree-l1"><a class="reference internal" href="session/index.html">Session</a></li>
<li class="toctree-l1"><a class="reference internal" href="http/index.html">HTTP</a></li>
<li class="toctree-l1"><a class="reference internal" href="jms.html">JMS</a></li>
<li class="toctree-l1"><a class="reference internal" href="realtime_monitoring/index.html">Realtime monitoring</a></li>
<li class="toctree-l1"><a class="reference internal" href="extensions/index.html">Extensions</a></li>
<li class="toctree-l1"><a class="reference internal" href="cookbook/index.html">Cookbook</a></li>
<li class="toctree-l1"><a class="reference internal" href="developing_gatling/index.html">Information for Gatling Developers</a></li>
<li class="toctree-l1"><a class="reference internal" href="project/index.html">Project Information</a></li>
</ul>
</div>
</div>
</div>
</div>
</article>
</main>
</div>
</div>
<div class="sidebar-wrap col-md-3 content-left-wrap">
<div id="secondary" class="widget-area" role="complementary" itemscope="itemscope"
itemtype="http://schema.org/WPSideBar">
<aside id="search-2" class="widget widget_search">
<form role="form" method="get" class="search-form" action="search.html">
<label>
<span class="screen-reader-text">Search through the documentation :</span>
<input type="search" class="search-field" placeholder="Search the documentation" name="q">
</label>
<input type="submit" class="search-submit" value="Search">
</form>
</aside>
<aside class="widget">
<h1 class="widget-title">Table of Content</h1>
<ul>
<li><a class="reference internal" href="#">Gatling</a><ul>
<li><a class="reference internal" href="#migrating-from-a-previous-version-of-gatling">Migrating from a previous version of Gatling</a></li>
<li><a class="reference internal" href="#user-s-guide">User’s guide</a></li>
</ul>
</li>
</ul>
</aside>
<aside class="widget">
<h1 class="widget-title">Next topic</h1>
<ul>
<li>
<a href="whats_new/index.html" title="Next Chapter: Migration guides">
Migration guides
</a>
</li>
</ul>
</aside>
<aside class="widget">
<h1 class="widget-title">Contribute</h1>
<ul>
<li>
<a href="https://github.com/gatling/gatling/edit/master/src/sphinx/index.rst">Edit this page on Github</a>
</li>
</ul>
</aside>
</div>
</div>