| Is there any better way than to issue tons of `p4 file` command with a | long list of file specs like "//depot/a#label1" "//depot/a#label2" on | each, then pawing through stderr for those that were bad and stdout for | which revisions the few ok labels apply to? Right now, I'm firing off | one `p4 files` per file in the source repo, each one with one spec per | label. I lifted that technique from one of the p4 compatible | repository browsers.

Specs like '//depot/a@label1' are horribly slow, as labels aren't sorted by depot file and thus must be scanned for each file. Alas, at this point there isn't a speedier option other than "p4 files @label1", "p4 files @label2", etc, and have the application (you) merge the results.

The fact that you're running one command per invocation is a little slow, too, I'm afraid, but again there's no easy way short of using the API or using 'p4 -s files x y z' and relying on the 1 response per argument.

Christopher