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

Re: Merging /branches/integrate-cache-membuffer to /trunk

From: Johan Corveleyn <jcorvel_at_gmail.com>
Date: Thu, 27 Jan 2011 01:56:48 +0100

On Wed, Jan 26, 2011 at 11:42 PM, Stefan Sperling <stsp_at_elego.de> wrote:
> On Wed, Jan 26, 2011 at 11:25:59PM +0100, Stefan Fuhrmann wrote:
>> Hi @all,
>>
>> I'm planning to merge said branch Monday 7th.
>> Speak now or forever hold your peace.
>>
>> Rationale:
>>
>> I've been testing / using that code for a while now
>> and am reasonably confident that it works. And it
>> is not exactly rocket science, either.
>>
>> Because a large portion of my other performance
>> work builds upon that low-latency caching feature,
>> it would really like to see it being merged. Directly
>> after the merge, I will make the feature strictly opt-in
>> instead of defaulting to a 16 or 64 MB cache.
>
> I'd say merging to trunk is perfectly fine if you're confident that
> there aren't any roadblock issues and it's not enabled by default anyway.
> We've released optional new features in the past (e.g. libsvn_serf).
> It's much more likely to get tested this way :)

Would there be a way to opt-in with a mod_dav_svn server? IIRC, you
have added some configuration options for svnserve, but not yet a way
to configure it with an apache server (unless I missed something).
Maybe you or someone else can add the necessary configuration
directives or anything else that needs to be done for this ...

I wouldn't want to miss out on the caching benefits, but for now I
wasn't too worried because I was content with a default of 64 MB.

Cheers,

-- 
Johan
Received on 2011-01-27 01:57:49 CET

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.