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

Re: Locking branch has been merged [Re: svn commit: r13571]

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2005-03-23 01:00:19 CET

On Mar 22, 2005, at 5:06 PM, Philip Martin wrote:

> Ben Collins-Sussman <sussman@collab.net> writes:
>> We've added three (const char *) fields and one apr_time_t to the
>> entry structure.
>> If we assume that most files will be unlocked most of the time, then
>> those four new fields will almost always be NULL. This will still be
>> a 20% memory increase?
> Yes. The svn_wc_entry_t structure itself has increased from 104 bytes
> to 124 bytes on my Linux box (3 x const char * == 3 x 4 bytes,
> apr_time_t == 8 bytes, 20 bytes total).

Okay, maybe lundblad can refresh my memory here. I'm looking at
svn_wc_entry_t, and I'm wondering why it's storing anything more than a
token-field. That's the only critical bit of authentication the
working copy needs to make use of a lock. Why do we have the entire
(potentially multi-line) lock-comment being cached in the entries file?

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Mar 23 01:01:32 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.