On Wed, Sep 26, 2018 at 02:45:29PM -0500, Brendon Colby wrote:
> Tc mean: 0.59 ms
> Tc std dev: 17.49 ms
> Tc max: 1033.00 ms
> Tc median: 0.00 ms
I don't know if all your servers are local, but if that's the case, the
Tc should always be very small and an stddev of 17ms and
Am 25.09.2018 um 01:08 schrieb Computerisms Corporation:
> if you are still with me, thank you so much for reading this far. I
> would truly appreciate any thoughts you might have on how to diagnose
> what is causing this issue...
While I don't have any idea from the top of my head your
I have a problem were I don't know were to look further and I hope I can
get some pointers. The problem is that during times with a high request
count sometimes answers for requests take a long time. So I identified
an request that took a long time and got the log entries from the
On Tue, Sep 25, 2018 at 10:51 PM Willy Tarreau wrote:
> Just be careful as you are allocating 64GB of RAM to the TCP stack.
Yeah, after I figured that out I set it down to 1M / 4GB ram which is
enough to handle peak traffic on only one proxy VM.
> As a hint, take a look at the
On Wed, Sep 26, 2018 at 12:09:07PM +0300, prog 76 wrote:
> First of all Thank you for this great product. We are very happy to use it
> for years.
> Unfortunately from version 1.8.12 we have an issue. Sometimes haproxy crash.
> We tried to upgrade to 1.8.13 and it also
Mail list logo