[p4] Is a 1500 line protect table excessive?

[David Ferguson]

Well, we actually went from about 1200 lines to 3300 and saw performance
improvements (20-30%)
The first set was heavy on wildcarding and exclusionary items in an attempt
to be succinct.
the second set had no wildcarding (except for trailing ...) and is completely
inclusionary.  As a result, it has has the nice feature of being extremely
simple to read and understand...
But, I have to say that the performance improvements, while significant
percentage-wise, were basically invisible to the user...  That is, the 'slow'
times were on the order of 2-3 ms slower than the 'faster' ones.

-daf
VMware 

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