P4 verify how long

The '-z' flag that instructs 'p4 verify' to optimize digest computations by skipping revisions of lazy copies. Can I speed it up? Set up another server that has the latest Perforce checkpoint restored and any incremental numbered journals as described in: Offline Checkpoints. Then, share the versioned files on the primary server as read-only, and access these files from the Off-line checkpoint server. On Unix systems, share the versioned files as a read-only NFS filesystem.

Mount the versioned files directories as read-only on the off-line server. Place appropriate symbolic links in the root directory of the off-line Perforce server to point to the NFS shares. Then, run p4 verify from the off-line server.

Whether you're looking for self-service resources, product downloads, or how to contact Technical Support, we've got lots of options to get the help you need—fast! Try Free Request Support. Sign in to ask the community. Helix Core Admin Tasks. This was added 4 years ago, in version This only applies to the files that sync actually transfers; the files that are already up-to-date on your workstation are not re-verified.

The purpose of the checksum verification is to detect damage or sabotage of the network or the server itself, and so it's quite useful. BryanPendleton : Would you mind providing some documentation on that? I'd like to update the answer. One place where this behavior is documented is in the server release notes ftp. Search for 'Bug ' or '' and you will see the release note I mean.

Not much doc, sorry, but better than nothing : — Bryan Pendleton. Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password. The server does not perfom well when doing a verify and having 30 people using it, it's a pity I can't have another computer. We have a seperate machine that rsyncs. Post by Robert Cowham A verify has to recalculate the digest and compare it with the stored one for every revision specified - otherwise it wouldn't detect files that have "gone bad" since verify was last done.

Thus I wouldn't expect it to be faster. What is faster is the verify -u since it should be pretty much unnecessary except for needing to be done once, and subsequently only for submits with old client versions. The MD5 digest is used when doing things like diffs, e. The backup server idea is a good one - tests your backups too. Post by Craig Allsop Yes, this feature doesn't help and the verify -qu only takes a couple of minutes.

The only way to perform a "true" check of the data is with the verify -q. If possible, you might consider running a p4 verify on a backup copy of the server in order to get a decent estimate of verification time.

Greetings, My current client has never as far as I can tell run "p4 verify" They have approximately changelists if that helps.

As I understand it p4 verify will lock the p4 database and make it unavailable for checkins while the verify step is being run. I'm trying to give the client and estimate of how long p4 will be unavailble. Rough 's are good. Post by Jeff Grills A verify checks the file contents for correctness, so it depends more upon the total size of all the revisions submitted into perforce rather than.