Marcin Kasperski wrote:
> ...
>
>Yeah, here the needs of people working remotely over the modem on
>typical software project (slow network + not so big files) are
>fairly different from the needs of the people working on the
>large project within organization (fast local network + a lot
>of, sometimes very large files, from which only part is edited).
>And I think to satisfy both one just should configure whether to
>keep the textbase as the client property.
>
>
Ditto. We've got a product so big that that working copies without
derived objects range from 1GB to 5GB. We regularly have to fight the
disk space problem as we try to support 5 different releases and do new
development on the next two. We use clearcase and resort to loading
subsets of views and using dynamic views (MVFS) for simple maintenance work.
Of course, we aren't typical. Any SCM system can't fulfill everyone's
needs. But if subversion want's to appeal to large development groups
with large products, they need to consider that more disk space is cheap
as a commodity, but somewhat expensive from an organizational
perspective. Workstations have only so many disk controllers and
usually don't have good volume management to make it simple to extend
the storage capacity of a system. So often times, adding more storage
requires partial system rebuilds (this is in the real world, not in the
geek world where everyone makes all the right decisions about drive
partitioning, uses OSes with disk spanning volume managers, and actually
uses those volume managers).
I'm not going polar-opposite-extreme on anyone...just pointing out that
the "disk space is cheap" argument has significant caveats in the real
world and when working on real life enterprise products.
Evan
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Mar 16 13:17:51 2004