[p4] Branch deprecation procedure?

[Dave Lewis]

On 9/19/07, Chuck Karish <chuck.karish at gmail.com> wrote:
> 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.
>
> I find this surprising.  Are you sure the exclusionary mappings didn't
> contain multiple wildcards?

I have also experienced high overhead when having protection mappings
with multiple wildcards.  when I refactored one of the wildcards to
explicit paths, turning it from one line into about  10, performance
went up by a factor of perhaps 60.

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

I have used a simple trigger which blocked checkins with a msg saying
the branch was closed, or whatever.  This is much less overhead than
the protection table.


dave

>
>
> --
> Chuck Karish   karish at well.com   (415) 317-0182
> _______________________________________________
> perforce-user mailing list  -  perforce-user at perforce.com
> http://maillist.perforce.com/mailman/listinfo/perforce-user
>