[p4] Is a 1500 line protect table excessive?
Chuck Karish
chuck.karish at gmail.com
Wed Dec 12 09:26:43 PST 2007
On Dec 11, 2007 1:49 PM, Ivey, William <william_ivey at bmc.com> wrote:
> I'd think so.
>
> I'm looking at the protect table of a server I wasn't the admin of and
>
> it is right around 1500 lines (all groups). Looks like the only
>
> wildcarded path sections are the usual trailing /...
>
> Some of the lines are probably obsolete and a lot of them can
>
> be replaced by making some groups sub-groups of others which
>
> would replace three protect lines by two at least.
>
>
>
> Does anyone have a feel for the performance impact this might
>
> have if we could cut it down by 30-40%? (Is it worth doing a major
>
> overhaul in the short term vs. whittling it down over time?)
My understanding is that the appropriate metric is the size of
the whole stack of maps that p4d has to compile, including the
client map and the branch map (the last for integrations only).
Interpreting maps eats CPU. This calculation can be done in
parallel, so it's possible to keep it from being a performance drag
by throwing more processors at the problem. It's not an emergency
unless your server system is running out of CPU cycles.
Think about order, too. I'd put rule sets for the busiest parts of
my depot at the bottom of the list.
--
Chuck Karish karish at well.com (415) 317-0182
More information about the perforce-user
mailing list