first of all I'd like to thank you for maintaining a great product!
HAProxy has been an essential part of ThredUP infrastructure
In particular it was super useful for traffic routing during a migration to
Kubernetes. HAProxy is one of our primary sources for
On Mon, Mar 04, 2019 at 02:44:38PM +0100, Tim Düsterhus wrote:
> One could limit the overall brotli resource usage by returning NULLs in
> the custom allocator when the *total* (versus the per-stream) brotli
> memory consumption exceeds a certain level. The handling of OOMs in the
> remaining code
Am 04.03.19 um 14:36 schrieb Willy Tarreau:
>>> can document such limits and let users decide on their own. We'll
>>> need the equivalent of maxzlibmem though (or better, we can reuse it
>>> to keep a single tunable and indicate it serves for any compression
>>> algo so that there isn't
On Wed, Feb 27, 2019 at 01:23:28PM +0100, Tim Düsterhus wrote:
> As mentioned in my reply to Aleks I don't have any numbers, because I
> don't know to get them. My knowledge of both HAProxy's internals and C
> is not strong enough to get those.
> The manpage documents this:
On Fri, Mar 01, 2019 at 12:33:57PM +0100, gdelafond+hapr...@aquaray.com wrote:
> > On 9 Jan 2019, at 11:06, gdelafond+hapr...@aquaray.com wrote:
> > Hello,
> > I try to understand how to use the -M ACL flag.
> > From the documentation :
> > The "-M" flag allows
On Mon, Mar 04, 2019 at 11:45:53AM +, Luke Seelenbinder wrote:
> Hi Willy,
> > Do you have "option abortonclose" in your config ?
> We do not have abortonclose. Do you recommend this if we have a lot of
> client-side request aborts (but not connection level closes)? From reading
> Do you have "option abortonclose" in your config ?
We do not have abortonclose. Do you recommend this if we have a lot of
client-side request aborts (but not connection level closes)? From reading the
docs, I came away conflicted as to the implications. :-)
Mail list logo