[p4] Any way to estimate how long p4 verify will take?

Tyler, Tom Tom.Tyler at Monster.com
Fri May 5 12:44:56 PDT 2006


Hello!

   Well, there are several factors that affect verify times, like I/O performance, CPU speed, and of course the amount of data you're looking at.

You mentioned 4,900 changelists -- that isn't very many.  If I make some bold (and unvalidated) assumptions about the size/scale of the Perforce installation based solely on the number of changelists, I'd be surprised if a verify in that case took longer than 20-30 minutes.  Our own server has ~5,300 changelists, and the verify runs in 17 minutes.  Now, we run verifies with script to break things up into manageable chunks, processing one depot at a time, and one high-level subdirectory at a time.  (The next upgrade for this script is to go deeper into the structure if necessary if it hits MaxScanRows/MaxResults limits).

The same script takes 8+ hours to run on large Perforce installations.  For that reason, we do daily verifies only on the backup/warm spare server, and run verifies on the primary/production server only if we suspect an issue.

Cheers!

Tom

-----Original Message-----
From: perforce-user-bounces at perforce.com
[mailto:perforce-user-bounces at perforce.com]On Behalf Of William Deegan
Sent: Thursday, April 20, 2006 4:45 PM
To: perforce-user at perforce.com
Subject: [p4] Any way to estimate how long p4 verify will take?


Greetings,

My current client has never (as far as I can tell) run "p4 verify"
They have approximately 4900 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.

Thanks,
Bill

_______________________________________________
perforce-user mailing list  -  perforce-user at perforce.com
http://maillist.perforce.com/mailman/listinfo/perforce-user


NOTICE:
This message may contain privileged or otherwise confidential information. If you are not the intended recipient, please immediately advise the sender by reply email and delete the message and any attachments without using, copying or disclosing the contents. (FE01)



More information about the perforce-user mailing list