Tony Butt wrote on Fri, Jul 08, 2011 at 13:56:07 +1000:
> On Fri, 2011-07-08 at 03:58 +0300, Daniel Shahaf wrote:
> > Tony Butt wrote on Fri, Jul 08, 2011 at 10:41:43 +1000:
> > > On Fri, 2011-07-08 at 02:59 +0300, Daniel Shahaf wrote:
> > > > This doesn't address memcached directly, but there has been a /lot/ of
> > > > work on server-side optimization and caching in 1.7 (also for
> > > > non-memcached-backed caches).
> > > >
> > > > http://subversion.apache.org/docs/release-notes/1.7#server-performance-tuning
> > > >
> > > > You might want to take 1.7.0-alpha3 for a spin...
> > > >
> > > Probably don't want to do that.
> > > We are in a commercial environment, with some 20 developers relying on
> > > subversion - not the time for an alpha release.
> > >
> >
> > I wasn't suggesting that you upgrade your production server!
> I didn't really think you would be :-)
> >
> > Just that you install the alpha in a test environment to see if it
> > improves the situation for you. (or if there is anything you see that
> > requires modification /before/ the release --- before compatibility
> > promises apply --- as in eg issue #3952)
> >
> My available test server also syncs the production repository to itself
> as a hot spare. I am probably brave enough to install 1.7.0-alpha3 on
> that, so long as there are no issues syncing from 1.6.17 to 1.7.0
>
In theory: should work.
In practice: we may have introduced bugs on trunk that no one has
unearthed yet.
Received on 2011-07-08 08:47:00 CEST