On Tue, Jun 21, 2011 at 10:27 AM, Stefan Sperling <stsp_at_elego.de> wrote:
> It's a bit worrying that our new default will require admins to tweak
> the server config to provide adequate performance for clients in
> the default configuration.
> Then again, there's the chicken-and-egg problem. If we don't force
> people to push for server-side config changes, they're never gonna
> Though maybe we should wait for one more release cycle before making
> serf the default, and tell people that to get most out of httpv2
> for 1.7 they should make sure their clients use serf and their
> server config is adjusted accordingly?
> That would provide some time for a soft transition. It might cause
> less pain for those who run into the problem with servers they
> do not control.
The admins will never change it until they have users clamoring for it.
My take is that as we go through the alpha and beta releases, we'll
hit the bigger sites and try to get them to tweak their setups. We
can then evaluate during the beta process what the default should be.
IMO, the point of the alpha/betas are to highlight and identify stuff
like this...so, I don't see a reason yet to change the default... --
Received on 2011-06-21 19:45:50 CEST