<p>Since last release a couple of features were added, namely:</p>
<ul>
<li>cancellation(via CTRL+C);</li>
<li>detailed error messages.</li>
</ul>
<p>Also, performance got a little better, mostly, because of the new SSA-backend. RPS went from roughly 176k(with 1.6) to 204k(with 1.7) on my machine, using "Hello, World"-style server.</p>
<p>With <a href="https://github.com/codesenberg/bombardier/releases/tag/v0.5">latest release</a> I get ~240k RPS.</p>
<p>For comparison, with <a href="https://github.com/rakyll/hey">hey</a>(previously known as boom) RPS is somewhere around 100k, using same server and hardware, but <em>hey</em> consumes much more memory - 120Mb(with bombardier) vs. 1.5Gb(with hey).</p>
<hr/>**评论：**<br/><br/>orbat: <pre><p>Oh nice. How's it compare to <a href="https://github.com/JoeDog/siege" rel="nofollow">siege</a>?</p></pre>MeatTenderizer: <pre><p>There's also <a href="https://github.com/tsenart/vegeta" rel="nofollow">Vegeta</a></p></pre>codesenberg: <pre><p>Actually, there is <a href="https://github.com/codesenberg/bombardier/wiki/Comparison-to-other-tools" rel="nofollow">this</a> wikipage. It has a <a href="https://github.com/codesenberg/bombardier/wiki/Comparison-to-other-tools#vegeta" rel="nofollow">section</a> about <em>Vegeta</em>.</p>
<p>AFAIK <em>Vegeta</em>'s garbage generation(high) and performance(low) haven't changed since then.</p>
<p>Feature-wise both tools are somewhat similar, expect for UI and some knobs(<em>Vegeta</em> supports multiple targets, HTTP/2, rate limiting, cert specification and redirects).</p></pre>sairamk: <pre><p>There is also <a href="https://github.com/rakyll/hey" rel="nofollow">hey</a></p></pre>codesenberg: <pre><p>Hi, my knowledge about <em>siege</em> is very limited, but from what I can tell, <em>siege</em> has some features, that <em>bombardier</em> doesn't, namely - redirect following, hitting urls from file(randomly).</p>
<p>On the other hand building <em>siege</em> on Windows is somewhat challenging(I'm not even sure if <em>siege</em> supports Windows). Also, <em>bombardier</em> features a nice progressbar :)</p>
<p>Performance-wise, on my Ubuntu VM I got ~7.3k RPS with <em>siege</em>, using this command on the same test server:</p>
<pre><code>siege -c 125 -t 10S -b --no-parser --no-follow http://localhost:8080
</code></pre>
<p>With <em>bombardier</em> I got ~87k RPS with same setup.</p>
<pre><code>bombardier http://localhost:8080
</code></pre>
<p>Hope this helps.</p></pre>orbat: <pre><p>It certainly does, thank you! Impressive performance.</p></pre>justinisrael: <pre><p>I currently use siege. Would like to know as well. </p></pre>dAnjou: <pre><p>This looks like a very useful tool for developers using any language and even people in related fields, yet it is - like many other projects - only posted in <a href="/r/golang" rel="nofollow">/r/golang</a>, a very limited audience.</p></pre>timetravelhunter: <pre><p>Without control over TLS session and ticket caching I can't use this.</p></pre>iends: <pre><p>Submit a PR. </p></pre>timetravelhunter: <pre><p>It requires changes to go crypto. They only support ticket session caching. </p></pre>iends: <pre><p>Submit a PR.</p></pre>timetravelhunter: <pre><p>Go doesn't use pull requests. </p></pre>iends: <pre><p>Submit a change request. </p></pre>timetravelhunter: <pre><p>I have. I've talked to a few core developers and they don't seem interested. </p></pre>
