On Thu, Jun 14, 2012 at 12:11 AM, Javier Guerra Giraldez <[email protected] > wrote:
> On Tue, Jun 12, 2012 at 8:58 AM, Loic d'Anterroches <[email protected]> > wrote: > > ab is HTTP 1.0 and Mongrel2 keeps long lived connection making ab > > benchmarks fail. > > try the -k option > > -- > > httperf runs much better, thank you. -k option did not work for ab. I assumed that sending a close message back to mongrel2 after each handler response should have been enough to trigger connections to be similar to HTTP 1.0? Is there something else in the protocol that is missing here? I had to remove the CONN.close statement from my handler as I assumed that was required; httperf now works fine (where ab hangs). Thanks again Jason
