[p4] depot filename vs. client filename

Robert Cowham robert at vaccaperna.co.uk
Thu Jul 6 11:04:59 PDT 2006


What version of Perforce server do you have?

Are you hitting the client mapstate problem as identified in:

http://www.perforce.com/perforce/conf2003/index.html#swamp 

This has "gone away" in 05.2 release.

Search for mapstate in
http://www.perforce.com/perforce/doc.052/user/relnotes.txt

Robert

> -----Original Message-----
> From: perforce-user-bounces at perforce.com 
> [mailto:perforce-user-bounces at perforce.com] On Behalf Of 
> Becker, Holger
> Sent: 05 July 2006 15:36
> To: perforce-user at perforce.com
> Subject: [p4] depot filename vs. client filename
> 
> Hi List,
> 
> we observe some performance issues with p4 stat depending on 
> the kind of filenames we use.
> 
> If we use the depot filename syntax like //foo/x/y/z.txt the 
> fstat command last longer than using the client filename like 
> c:\myperforce\x\y\z.txt.
> 
> This seems to depend on the client spec layout. The fstat 
> command with depot filename syntax becomes rather slower if 
> the client spec excludes some directories with wildcards. The 
> fstat command with client filename doesn't show this behaviour.
> 
> We use the depot filename syntax in some perl scripts so we 
> are wondering if we have to change these scrips.
> 
> I couldn't find anything on the list archive about this problem.
> 
> Thanks in advance for any hint.
> 
> Regards
> Holger
> 
> _______________________________________________
> perforce-user mailing list  -  perforce-user at perforce.com 
> http://maillist.perforce.com/mailman/listinfo/perforce-user
> 
> 



More information about the perforce-user mailing list