title: Gatling vs httperf
body: <p>I am trying to stress test one simple server with 10K connections per seconds; it's pretty dummy server so this should be possible.</p>
  
  <p>When I run gatling, the best I can get is 7K, at 8K we start to receive connection errors. This is again a simple test, ramping to 8k and holding the traffic for 2 minutes.</p>
  
  <pre><code>Request 'Home' failed: java.net.ConnectException: Cannot assign requested address
  </code></pre>
  
  <p>I know this error is related to tuning our box (open files etc). I have tried some commands, but that didn't help much.</p>
  
  <p>Anyway, when I run a simple burst test with httperf, I easily get 10K without any errors. Command line:</p>
  
  <pre><code>httperf --uri / --server cloud-10-0-20-35 --port 8080 --num-conns=500000 --rate 10000
  </code></pre>
  
  <p>Im on Centos 6.x VM box.</p>
  
  <p>Why httperf is working different? I know its a native tool, but why such big difference? Any ideas? I am aware that this is more related of java infrastructure, then to Gatling itself - that is awesome tool.</p>