Re: Philip, is issue #1556 easy for you?

Not to appear too naive about these things, but shouldn't there be a point at
which XXXX number of locks translates to a single lock on the entire working
copy or the repository, or what not?

To make an analogy, on a RDMBS, if I ask for a large number of things, if my
settings on the RDBMS are correct, a table wide lock is issued and performance
does not degrade. But if the settings are wrong, and each row is locked
indiscriminately, performance degrades as a function of N, sometimes O(N), at
others O(2N) and I've even seen it as O(N^1.5) or as bad as O(N^2).

I don't know if it's specifically applicable to your problem. Just hoping it
might be helpful to think about.

-- 
Shamim Islam
BA BS
Philip Martin said:
> kfogel@collab.net writes:
>
>> Sander, Mike, Ben, and I were just discussing issue #1556, the
>> "mysterious post-update/checkout delay on huge trees" bug.
>
> I'm not sure what you want the feedback to look like, just one single
> "please wait" message?  Is that just a single notify call added to
> svn_client_update()?  I'm guessing you don't want a notify call for
> each directory unlocked.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org