It can be useful to have a server-side view of the end-to-end time for a
request to be served, such as a tool like cURL would do on client side.
HAProxy provides Tt timer for this, but unfortunately, it is accounting
idle time too, which can be very long when using HTTP keep-alive, hence
providing
Hi Damien,
On Thu, Apr 16, 2020 at 01:27:50PM +, Damien Claisse wrote:
> It can be useful to have a server-side view of the end-to-end time for a
> request to be served, such as a tool like cURL would do on client side.
> HAProxy provides Tt timer for this, but unfortunately, it is accounting
Hi Willy,
Le 16/04/2020 17:00, « Willy Tarreau » a écrit :
I'm a bit confused by how it can be efficiently used. Because it still
includes the client-side handshake which only happens before the first
request, so if you're interested in removing idle time from keep-alive
request
Hi Damien,
On Thu, Apr 16, 2020 at 04:03:19PM +, Damien Claisse wrote:
> What I'm actually interested in is assessing real-world total time taken to
> serve a client request (as seen from the client such as reported by cURL or
> in a browser network performance tab, except for DNS lookup time)
4 matches
Mail list logo