[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: lock scalability

From: John Peacock <jpeacock_at_rowman.com>
Date: 2005-03-14 20:55:10 CET

Greg Hudson wrote:
> (c) I'm not personally going to be very sad if such people find that
> locking large numbers of files consumes large amounts of resources. In
> my mind, mass file locking isn't a very good way of doing work, so if
> the system pushes back on people who try it, that's not a terrible
> thing.

My reading of what Sussman said:

> * just like property lists, both sides of the network currently hold
> unbounded lists of lock-objects in memory.

suggests that too many locks could potentially crash the server and/or
client. Has anyone done a "back of the napkin" calculation to see at
what point the list of lock-objects is likely to exceed the existing
memory footprint of Subversion? What is sizeof(lock-object)? What do
you consider "large amounts of resources" in this context (are we
talking MB or GB or are you talking about CPU cycles)?


John Peacock
Director of Information Research and Technology
Rowman & Littlefield Publishing Group
4501 Forbes Boulevard
Suite H
Lanham, MD  20706
301-459-3366 x.5010
fax 301-429-5748
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Mar 14 20:56:09 2005

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.