3 messages in com.perforce.perforce-user"p4 dirs" is slow
FromSent OnAttachments
Gare...@organic.com11 Jun 1999 08:38 
Amau...@atsm.fr11 Jun 1999 09:00 
Jeff...@nextcard.com11 Jun 1999 09:05 
Subject:"p4 dirs" is slow
From:Amau...@atsm.fr (Amau@atsm.fr)
Date:06/11/1999 09:00:14 AM
List:com.perforce.perforce-user

I asked this to Perforce support some time ago. Just quote the arguments: p4 dirs "//depot/main/src/*"

I believe this is because the NT command interpreter tries to expand the wildcard: //depot/main/src/* looks like a UNC path to the system.

the NT command dir //depot/main/src/* is exactly as slow as Perforce commands !

This doesn't happen with '...', as this is not correct in NT filenames.

---Amaury

I'm trying to write a script that writes out the tree structure of a Perforce depot (just head revisions, ignoring history). It's recursive, using "p4 dirs" to obtain the children of each directory. My problem is that "p4 dirs" can take several seconds to execute if there are no child directories (though it doesn't always). My depot is very small with only about 40 files and directories in it, and my server's running NT. I'd like the script to be quick enough to use as a CGI. Does anyone have any ideas on why this is slow?

Thanks, --Gareth

Gareth Rowlands Senior Server Engineer Organic +44 (0171) 6442608