On Thu, Sep 4, 2008 at 4:20 AM, Willy Tarreau <w#1wt.eu> wrote:
>
> I'm stupid, I found this morning why you see short timers in your logs.
> It's simply because your frontend is full. The connection between your
> client and haproxy does not really establish, your connection establishes
> between the client and the SYSTEM (your connection lies in the backlog
> queue). And the system will wake haproxy up once the frontend releases
> one connection slot by closing one connection. Haproxy starts the accept()
> timer at this precise moment (because it could not even know there was
> something pending, the system was keeping it), and if your request is
> fast to process, you have a small timer as above (eg: 17 ms after waiting
> 1 minute in the system).
ah, ok - the system!!! that certainly helps to clarify things. Thanks for that note - i missed that as well.
> As a hint, you might see in your logs that the
> connection which ended just before yours got processed took approximately
> the time you spent waiting.
>
right.. thanks!!!
-jf
-- In the meantime, here is your PSA: "It's so hard to write a graphics driver that open-sourcing it would not help." -- Andrew Fear, Software Product Manager, NVIDIA Corporation http://kerneltrap.org/node/7228Received on 2008/09/04 03:41
This archive was generated by hypermail 2.2.0 : 2008/09/04 03:46 CEST