[p4] Is a 1500 line protect table excessive?

[Tetlow, Gordon]

A lot of it would depend on how the table was structured.

The protect table is scanned twice from the bottom up, first match
winning. The first pass is to see if the user even has permission to
know if the depot path is there. The other is for the actual permission
needed.

So if you were to put:
list user * * //depot/...
as the last line in your protect table, you would effectively take care
of the first pass (of course, this can be constrained by security).

If you have broader permission lines, try to put them at the bottom of
the table, which will cause the protect table scan to finish as quickly
as possible.

-gordon 

-----Original Message-----
From: perforce-user-bounces at perforce.com
[mailto:perforce-user-bounces at perforce.com] On Behalf Of Ivey, William
Sent: Tuesday, December 11, 2007 1:49 PM
To: Perforce User
Subject: [p4] Is a 1500 line protect table excessive?

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?)

 

Thanks.

 

-Wm

 

 

 

_______________________________________________
perforce-user mailing list  -  perforce-user at perforce.com
http://maillist.perforce.com/mailman/listinfo/perforce-user