Re: eliminating sequential bottlenecks for huge commit and merge ops

2012-01-08 Thread Stefan Fuhrmann
On 05.01.2012 01:35, Daniel Shahaf wrote: Greg Stein wrote on Wed, Jan 04, 2012 at 19:08:41 -0500: (*) I'd be interested in what they are doing. Is this a use case we might see elsewhere? Or is this something silly they are doing, that would not be seen elsewhere? They use the Apache CMS[1] to

Re: eliminating sequential bottlenecks for huge commit and merge ops

2012-01-05 Thread Peter Samuelson
[Joe Schaefer] > They're using the ASF CMS to manage the www.openoffice.org website, > which is full of 10 years worth of accumulated legacy spanning 50 or > so different natural languages. The CMS is "too slow" during commits > to template files or such which change the generated html content of

Re: eliminating sequential bottlenecks for huge commit and merge ops

2012-01-04 Thread Joe Schaefer
> > From: Greg Stein >To: Joe Schaefer >Cc: "dev@subversion.apache.org" >Sent: Wednesday, January 4, 2012 7:54 PM >Subject: Re: eliminating sequential bottlenecks for huge commit and merge ops > > > >On Ja

Re: eliminating sequential bottlenecks for huge commit and merge ops

2012-01-04 Thread Greg Stein
On Jan 4, 2012 7:20 PM, "Joe Schaefer" wrote: >... > They're using the ASF CMS to manage the www.openoffice.org website, which is full > of 10 years worth of accumulated legacy spanning 50 or so different natural languages. > The CMS is "too slow" during commits to template files or such which cha

Re: eliminating sequential bottlenecks for huge commit and merge ops

2012-01-04 Thread Daniel Shahaf
Greg Stein wrote on Wed, Jan 04, 2012 at 19:08:41 -0500: > (*) I'd be interested in what they are doing. Is this a use case we might > see elsewhere? Or is this something silly they are doing, that would not be > seen elsewhere? They use the Apache CMS[1] to manage their site[2,3]. Some changes (

Re: eliminating sequential bottlenecks for huge commit and merge ops

2012-01-04 Thread Joe Schaefer
> > From: Greg Stein >To: Joe Schaefer >Cc: dev@subversion.apache.org >Sent: Wednesday, January 4, 2012 7:08 PM >Subject: Re: eliminating sequential bottlenecks for huge commit and merge ops > > > >On Jan 4, 2012 1:34 PM, "Jo

Re: eliminating sequential bottlenecks for huge commit and merge ops

2012-01-04 Thread Greg Stein
On Jan 4, 2012 1:34 PM, "Joe Schaefer" wrote: > > As Daniel mentioned to me on irc, subversion doesn't use threading > internally, so things like client side commit processing and merge > operations are done one file at at time IIUC. > > Over in the openoffice podling we have a use-case for a 9GB

eliminating sequential bottlenecks for huge commit and merge ops

2012-01-04 Thread Joe Schaefer
As Daniel mentioned to me on irc, subversion doesn't use threading internally, so things like client side commit processing and merge operations are done one file at at time IIUC. Over in the openoffice podling we have a use-case for a 9GB working copy that regularly sees churn on each file in the