From my personal experience, the performance hit when doing SVN operations
on a network drive instead of a local disk is severe. We have to use such
a setup as there is no real alternative to it.
It's related to doing synchrone writes over the network and waiting for ACK
packets. Every few hundered kByte are transfered in a SEND-ACK-SEND-ACK fashion,
each packet punished by the network delay.
I already asked over at the developer's list if they are interested in fixing
this, but it seems the aren't ..
-----Ursprüngliche Nachricht-----
Von: Méresse Christophe [mailto:christophe.meresse@nagra.com]
Gesendet: Freitag, 24. Februar 2006 16:02
An: bruno2.boudinski@worldonline.fr; users@subversion.tigris.org
Betreff: RE: Re: 'good practices' in php programming with subversion
> > My preference (and what we do with our Java web app):
> > Each dev has his own working copy
> > Each dev has, on his desktop, a unit testing environment
> > The central dev server is used for integration testing of
> all changes.
> > Code only gets to this server via svn checkout, developers cannot
> > copy files to it directly.
>
> Yes, but 'testing environment' mean apache+php on each dev desktop :-(
>
> This is what I would like to avoid... (but no better idea...)
Why not having the users's svn workspaces on a unix server accessible
- with samba to develop and do the svn operations,
- localy on the unix server by apache+php for the test purpose.
Christophe
---------------------------------------------------------------------
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
Received on Fri Feb 24 16:28:35 2006