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
>> <blair_at_orcaware.com>
>> Subversion training, consulting and support
>> http://www.orcaware.com/svn/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-02-16 00:02:40 CET