It helps when I remember to CC the list...
This is what I get from subversion --version,
Subversion Client, version 0.8.0
compiled Jan 30 2002, 18:34:14
I downloaded the most recent tar file, and checked out from the trunk
like the readme instructions said. I built the software from there. I
believe that is the version I am running.
If I don't have a recent enough version of the source let me know, I
will grab a newer one and build it. I'll update the bug when I get a
chance.
Thanks,
Kirby
Karl Fogel wrote:
> Thanks for the report from the field...
>
> Yah, we are aware of the memory issues and are working on them (some
> have been fixed very recently; you didn't say what version of
> Subversion you were using, so don't know if your test included the
> improved code).
>
> If you're feeling ambitious, you could make your test data and stats
> available in some concrete form and annotate
>
> http://subversion.tigris.org/issues/show_bug.cgi?id=602
>
> accordingly (possibly changing its summary, or creating a new issue,
> as you think appropriate). But no pressure, only get as involved as
> you have time for. :-) We'll fix the memory problems either way.
>
> Thanks,
> -Karl
>
> "Kirby C. Bohling" <kbohling@birddog.com> writes:
>
>>SubVersionists,
>>
>>I am currently interested in replacing CVS. I have evaluated several
>>different source repositories. SVN is very interesting, and looks
>>like a candidate for my replacement (I will wait for it to be finished
>>of course).
>>
>>So in the interest of tinkering with it, I took my current CVS
>>repository and checked out about 9 months worth of install tags (think
>>230 revisions). The source code is roughly 10-12MB. I did an export
>>from CVS, checked into SVN then exported out successive versions of
>>CVS did a diff, applied the patch and SVN checked in the result. Once
>>I got this up and running then I could play with it to my hearts
>>content with a real amount of data in it.
>>
>>I have two concerns to point out. I have searched the archives for
>>similar things, but I have yet to find them. One is that the same
>>repository in CVS takes about 130MB of disk space, and has 2 years
>>worth of revisions. The SVN was at 1.3GB when I completely ran the
>>filesystem out of space and had 8-9 months and was missing several of
>>the huge files from early in the CVS tree that had been removed. The
>>second is while check in's take a lot of memory, check outs take more.
>>I have roughly 300MB of VM on my linux machine, and I literally
>>couldn't check out trees that I had used for a year in CVS. The
>>directory had 1000 5-10K files that I was using as data for a
>>regression test. I can give you as much or as little information as
>>you want if this is a new issue. I probably can't give you the real
>>data (NDA's are like that *grin*).
>>
>>I think SVN has a serious shot at being a CVS killer, and addressing
>>these two issues will go a long way with me to getting me to switch
>>when SVN is ready for prime time. I was unsure if I should present
>>them here or put them in as bugs/features. My apologies if I choose
>>poorly.
>>
>> Thanks,
>>
Kirby
>>
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
>>For additional commands, e-mail: dev-help@subversion.tigris.org
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:37:03 2006