[p4] Branch deprecation procedure?

[Frank Compagner]

I had a look, and we did also have a couple of exclusionary mappings
with multiple wildcards in there. But those had been in there for
years without giving any performance problems. The problems definitely
started when I added the 20 lines as below; maybe it was the
combination that triggered it. To be on the safe side, I took out all
exclusionary mappings after that, as they weren't that important anyway.

Using a trigger will work fine if you want to block write access, but
I beleive the OP wanted to hide the branch from users so as not to
confuse them they're browsing the depot.

----------------------------------------------------------------
Frank Compagner                                  Guerrilla Games

CK> On 9/19/07, Frank Compagner <frank.compagner at guerrilla-games.com> wrote:
>> Yes, but make sure you understand the performance impact of
>> exclusionary mappings. Some time ago I decided to hide about 20
>> obsolete branches with lines in the protect table like this:
>>
>> write  group  *  *  -//depot/oldbranch1/...
>>
>> This brought the server to it's knees. Cpu usage was 100% all the
>> time, and even the simplest queries would take minutes to complete.

CK> I find this surprising.  Are you sure the exclusionary mappings didn't
CK> contain multiple wildcards?

CK> Another strategy I don't think we've mentioned: use a trigger to
CK> block writes.