Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [stellation-res] A database proposal, for fixing 22135.

On Fri, Aug 09, 2002 at 10:00:07PM +0000, Mark C. Chu-Carroll wrote:
> Time is definitely a concern. But I think that performance can be
> respectable using RDB storage. ClearCase uses an RDB for
> the backend storage, and uses a storage format for text that's
> very similar to what we're looking it, and it's no slouch on speed.

I am working with a ClearCase repository housing 6M lines of code 
and with hundreds of changesets added weekly. I  t  i  s  s  l  o  w  .
It is fine in the weekends when there are at most five people in the
office. During weekdays, with a couple hundreds people checking
in/out/compiling/grepping/diffing it is a pain.

>                                                                     Perforce
> uses an RDB for storage, and has a reputation as being
> lightning fast. 

I have heard good things about Perforce but haven't experienced it
first-hand and not on a large scale.

> > > I'd rather spend the time to change the schema so that it isn't
> > > so bad, than to give up on the database for storage.
> >
> > OK. Let's move on.
> 
> If you're convinced, sure. If not - I'm willing to continue discussing it,
> and I'm willing to be convinced that I'm on the wrong path. I'm also
> willing to respect the wishes of the rest of the team if everyone who
> cares disagrees with me. 

I am not convinced, but you know better the insides and the
capabilities of the code, and also have a long term vision that I'm
lacking at the moment. My concerns right now revolve around the
performance issues that slows down the test development. For instance,
if the checkin/checkout code would have been faster, I would have set
the default to 8-9 ages for the SimpleAgingFile and we would have caught
the repository bug 10 days earlier.

Also Dave strongly supports the database as the [only] backend.

Let's try to get the code in better shape and with a good test suite and
we can rethink/refactor later.

> By the way, has your Eclipse commit password come through yet?
> I haven't heard from them since I sent the vote results off to the
> admins.

The account has been activated yesterday but I didn't have time to sort
my tests out. I am planning to import the latest version of the unit
tests tomorrow.

florin

-- 

"If it's not broken, let's fix it till it is."

41A9 2BDE 8E11 F1C5 87A6  03EE 34B3 E075 3B90 DFE4

Attachment: pgp_4HI0z508p.pgp
Description: PGP signature


Back to the top