Jetty configuration about max pending requests

[zloster]

Currently the dropwizard performance for the simpler testcases (plaintext and json) is almost flat. That suggests that there is some serious restriction somewhere. The other jetty tests suggest that there should be better performance. Good place to start seems to be the default dropwizard config about the max request to queue before blocking the acceptor threads.

maxQueuedRequests 1024 The maximum number of requests to queue before blocking the acceptors.

http://www.dropwizard.io/1.1.0/docs/manual/configuration.html#all

[zloster]

The pull request is submitted. 3175 is the PR. dropwizard with MySQL should be affected - plaintext, json and the database tests.

[zloster]

There is a big problem with this change. I'll revert it - the results in JSON are half RPS than before the change.

[zloster]

Revert submitted. The result should be checked.
Edit: there is NO run yet on the ServerCentral environment (or Azure).

[zloster]

Solving this requires a lot more effort and profiling of the running application. Will wait for better days.
Eventually...