[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: serf and sourceforge.net don't get along (was on users@: Re: 1.7.0-alpha1 feedback)

From: Bolstridge, Andrew <andy.bolstridge_at_intergraph.com>
Date: Wed, 22 Jun 2011 14:51:37 +0000

> -----Original Message-----
> From: Stefan Sperling [mailto:stsp_at_elego.de]
> Sent: 21 June 2011 18:27
> To: Justin Erenkrantz
> Cc: Greg Stein; Daniel Shahaf; dev_at_subversion.apache.org; OBones; Uwe
> Schuster
> Subject: Re: serf and sourceforge.net don't get along (was on users@: Re:
> 1.7.0-alpha1 feedback)
> On Tue, Jun 21, 2011 at 10:18:24AM -0700, Justin Erenkrantz wrote:
> > On Tue, Jun 21, 2011 at 9:57 AM, Greg Stein <gstein_at_gmail.com> wrote:
> > > That definitely implies something wrong on the client. If the server
> > > is slow, then the client should mostly be blocking.
> > >
> 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 happen...
> 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?

Absolutely. The first thing to do is provide serf as a 2nd option, make a big song and dance about how great it is, and basically advertise the fact that it is there (from a user perspective). Then users can be encouraged to enable it and try it. This will require one of those blog posts from collabnet and a couple of web articles, along with super-easy-to-follow instructions for enabling it.
Some people will try it, they will find this kind of issue and report them to the appropriate server admin, and all the time it won't affect the reputation of SVN. If you do deliver serf enabled by default, then all perf issues will be seen to be the fault of SVN and we'll have unhappy users, even more comments like "git works great, upgrade to git" and suchlike.

Once the message that serf exists is out and widely known, then you can enable it by default in a later release, with the caveat that if server configuration cannot be made the user should "downgrade" to neon. That'll go over a lot better than enabling serf right now.
Received on 2011-06-22 16:52:29 CEST

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.