Great, thanks WIlly. Enjoy! :-)
Marcin Deranek
On Sat, May 16, 2020 at 10:40 PM Willy Tarreau wrote:
> Hi Marcin,
>
> On Sat, May 16, 2020 at 04:31:30PM +0200, Marcin Deranek wrote:
> > Actually I split this into 3 (see attachments):
> > 1. Adds improved swrate_rate_dynamic function
> > 2.
Hi Marcin,
On Sat, May 16, 2020 at 04:31:30PM +0200, Marcin Deranek wrote:
> Actually I split this into 3 (see attachments):
> 1. Adds improved swrate_rate_dynamic function
> 2. Adds proper req_tot metric for a server (as we have for frontend/backend)
> 3. Updates the code to use the new function
Hi Willy,
On Fri, May 15, 2020 at 2:45 PM Willy Tarreau wrote:
> What I'd like to see for the ctime etc is:
> - average over the number of samples like you did, but still per request
> ;
> - possibly new sets of per-connection metrics if these have some values
> to you (I guess they
Hi Marcin,
On Thu, May 14, 2020 at 01:23:50PM +0200, Marcin Deranek wrote:
> > The current ctime reports the avg time experienced by the
> > last 1024 *requests* and is documented as such, so when you want to think
> > in terms of user experience it's the one to consider. For example, if you
> >
Hi Willy,
On Wed, May 13, 2020 at 11:25 AM Willy Tarreau wrote:
> Hi Marcin!
>
> On Tue, May 12, 2020 at 12:17:19PM +0200, Marcin Deranek wrote:
> > Hi,
> >
> > Not a long ago while investigating some issues with one of the services I
> > stumbled across Connect Time (based on ctime metric)
5 matches
Mail list logo
