You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Chris Morris <th...@gmail.com> on 2008/02/15 02:52:12 UTC
Repository structure advice
If this is a FAQ somewhere, please redirect me.
Working at a shop with several products/codebases. Been running CVS for many
of them, SourceSafe for the rest - and currently porting to SVN. Each
codebase will need its own release branches (following the simple Prag
Version Control release branch approach).
Looking for any practical pros/cons of having one repository with all
products/codebases in it -- or many repositories, one per product/codebase.
--
Chris
http://clabs.org
Re: Repository structure advice
Posted by Blair Zajac <bl...@orcaware.com>.
No, 20 users wouldn't be an issue.
It's just how many commits/sec that matters, which for 20 users would be pretty
small.
Blair
Listman wrote:
>
> sorry i top posted my intial reply and screwed up the sequence of this
> thread.. i guess i'll have to keep going now..
>
> in our situation we might operating on hundreds of objects using
> --targets . in this case would a single repos with, say 20 users, be an
> issue in your opinion?
>
>
> On Feb 15, 2008, at 3:02 PM- Feb 15, 2008, Blair Zajac wrote:
>
>> No, that won't be an issue unless you're doing 100's of commits per
>> second.
>>
>> You'll find more time being spent in post-commit work, say backups and
>> generating emails, RRS feeds, etc, then in the actual commit.
>>
>> Also, there's only contention when the transaction is going to be
>> committed, there can be multiple transactions in progress all at the
>> same time. The serialization only happens when a transaction is being
>> promoted to a revision.
>>
>> Blair
>>
>> Listman wrote:
>>> the problem with using only one repository is that for large numbers
>>> of users with lots of checkins you could run into wait-times while
>>> the repos deals with the multiple simultaneous checkins, i think.. i
>>> believe that repos access is sequential, no?
>>> On Feb 14, 2008, at 8:03 PM- Feb 14, 2008, Blair Zajac wrote:
>>>>
>>>> On Feb 14, 2008, at 6:52 PM, Chris Morris wrote:
>>>>
>>>>> If this is a FAQ somewhere, please redirect me.
>>>>>
>>>>> Working at a shop with several products/codebases. Been running CVS
>>>>> for many of them, SourceSafe for the rest - and currently porting
>>>>> to SVN. Each codebase will need its own release branches (following
>>>>> the simple Prag Version Control release branch approach).
>>>>>
>>>>> Looking for any practical pros/cons of having one repository with
>>>>> all products/codebases in it -- or many repositories, one per
>>>>> product/codebase.
>>>>
>>>> Use one repository and have your trunk/tags/branches under each
>>>> separate project. It's much easier to manage and if you ever want
>>>> to move projects around, you can do it without dumping and loading.
>>>>
>>>> If you have different styles of data in one, say code, versus large
>>>> graphics in another, then you can split them up.
>>>>
>>>> Regards,
>>>> Blair
>>>>
>>>> --Blair Zajac, Ph.D.
>>>> CTO, OrcaWare Technologies
>>>> <bl...@orcaware.com>
>>>> Subversion training, consulting and support
>>>> http://www.orcaware.com/svn/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Repository structure advice
Posted by Listman <li...@burble.net>.
sorry i top posted my intial reply and screwed up the sequence of this
thread.. i guess i'll have to keep going now..
in our situation we might operating on hundreds of objects using --
targets . in this case would a single repos with, say 20 users, be an
issue in your opinion?
On Feb 15, 2008, at 3:02 PM- Feb 15, 2008, Blair Zajac wrote:
> No, that won't be an issue unless you're doing 100's of commits per
> second.
>
> You'll find more time being spent in post-commit work, say backups
> and generating emails, RRS feeds, etc, then in the actual commit.
>
> Also, there's only contention when the transaction is going to be
> committed, there can be multiple transactions in progress all at the
> same time. The serialization only happens when a transaction is
> being promoted to a revision.
>
> Blair
>
> Listman wrote:
>> the problem with using only one repository is that for large
>> numbers of users with lots of checkins you could run into wait-
>> times while the repos deals with the multiple simultaneous
>> checkins, i think.. i believe that repos access is sequential, no?
>> On Feb 14, 2008, at 8:03 PM- Feb 14, 2008, Blair Zajac wrote:
>>>
>>> On Feb 14, 2008, at 6:52 PM, Chris Morris wrote:
>>>
>>>> If this is a FAQ somewhere, please redirect me.
>>>>
>>>> Working at a shop with several products/codebases. Been running
>>>> CVS for many of them, SourceSafe for the rest - and currently
>>>> porting to SVN. Each codebase will need its own release branches
>>>> (following the simple Prag Version Control release branch
>>>> approach).
>>>>
>>>> Looking for any practical pros/cons of having one repository with
>>>> all products/codebases in it -- or many repositories, one per
>>>> product/codebase.
>>>
>>> Use one repository and have your trunk/tags/branches under each
>>> separate project. It's much easier to manage and if you ever want
>>> to move projects around, you can do it without dumping and loading.
>>>
>>> If you have different styles of data in one, say code, versus
>>> large graphics in another, then you can split them up.
>>>
>>> Regards,
>>> Blair
>>>
>>> --Blair Zajac, Ph.D.
>>> CTO, OrcaWare Technologies
>>> <bl...@orcaware.com>
>>> Subversion training, consulting and support
>>> http://www.orcaware.com/svn/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Repository structure advice
Posted by Blair Zajac <bl...@orcaware.com>.
No, that won't be an issue unless you're doing 100's of commits per second.
You'll find more time being spent in post-commit work, say backups and
generating emails, RRS feeds, etc, then in the actual commit.
Also, there's only contention when the transaction is going to be committed,
there can be multiple transactions in progress all at the same time. The
serialization only happens when a transaction is being promoted to a revision.
Blair
Listman wrote:
>
> the problem with using only one repository is that for large numbers of
> users with lots of checkins you could run into wait-times while the
> repos deals with the multiple simultaneous checkins, i think.. i believe
> that repos access is sequential, no?
>
>
> On Feb 14, 2008, at 8:03 PM- Feb 14, 2008, Blair Zajac wrote:
>
>>
>> On Feb 14, 2008, at 6:52 PM, Chris Morris wrote:
>>
>>> If this is a FAQ somewhere, please redirect me.
>>>
>>> Working at a shop with several products/codebases. Been running CVS
>>> for many of them, SourceSafe for the rest - and currently porting to
>>> SVN. Each codebase will need its own release branches (following the
>>> simple Prag Version Control release branch approach).
>>>
>>> Looking for any practical pros/cons of having one repository with all
>>> products/codebases in it -- or many repositories, one per
>>> product/codebase.
>>
>> Use one repository and have your trunk/tags/branches under each
>> separate project. It's much easier to manage and if you ever want to
>> move projects around, you can do it without dumping and loading.
>>
>> If you have different styles of data in one, say code, versus large
>> graphics in another, then you can split them up.
>>
>> Regards,
>> Blair
>>
>> --Blair Zajac, Ph.D.
>> CTO, OrcaWare Technologies
>> <bl...@orcaware.com>
>> Subversion training, consulting and support
>> http://www.orcaware.com/svn/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Repository structure advice
Posted by Listman <li...@burble.net>.
the problem with using only one repository is that for large numbers
of users with lots of checkins you could run into wait-times while the
repos deals with the multiple simultaneous checkins, i think.. i
believe that repos access is sequential, no?
On Feb 14, 2008, at 8:03 PM- Feb 14, 2008, Blair Zajac wrote:
>
> On Feb 14, 2008, at 6:52 PM, Chris Morris wrote:
>
>> If this is a FAQ somewhere, please redirect me.
>>
>> Working at a shop with several products/codebases. Been running CVS
>> for many of them, SourceSafe for the rest - and currently porting
>> to SVN. Each codebase will need its own release branches (following
>> the simple Prag Version Control release branch approach).
>>
>> Looking for any practical pros/cons of having one repository with
>> all products/codebases in it -- or many repositories, one per
>> product/codebase.
>
> Use one repository and have your trunk/tags/branches under each
> separate project. It's much easier to manage and if you ever want
> to move projects around, you can do it without dumping and loading.
>
> If you have different styles of data in one, say code, versus large
> graphics in another, then you can split them up.
>
> Regards,
> Blair
>
> --
> Blair Zajac, Ph.D.
> CTO, OrcaWare Technologies
> <bl...@orcaware.com>
> Subversion training, consulting and support
> http://www.orcaware.com/svn/
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Repository structure advice
Posted by Blair Zajac <bl...@orcaware.com>.
On Feb 14, 2008, at 6:52 PM, Chris Morris wrote:
> If this is a FAQ somewhere, please redirect me.
>
> Working at a shop with several products/codebases. Been running CVS
> for many of them, SourceSafe for the rest - and currently porting to
> SVN. Each codebase will need its own release branches (following the
> simple Prag Version Control release branch approach).
>
> Looking for any practical pros/cons of having one repository with
> all products/codebases in it -- or many repositories, one per
> product/codebase.
Use one repository and have your trunk/tags/branches under each
separate project. It's much easier to manage and if you ever want to
move projects around, you can do it without dumping and loading.
If you have different styles of data in one, say code, versus large
graphics in another, then you can split them up.
Regards,
Blair
--
Blair Zajac, Ph.D.
CTO, OrcaWare Technologies
<bl...@orcaware.com>
Subversion training, consulting and support
http://www.orcaware.com/svn/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org