[p4] Very big Perforce file : db.have

[Jeff Grills]

I've worked in environments where db.have was well over 20gb.  It's size is
a dependent upon the number of files that all the clients have sync'd from
perforce - with a big project and a lot of developers, you can get there
fast.

You can potentially shrink the db files by checkpointing and restoring.
Information on that process is here:
http://www.perforce.com/perforce/doc.061/manuals/p4sag/07_perftune.html#1055
420.  Apparently you don't have to do this as often in newer versions of
perforce (2005.1 and above) - see #68043 in the p4d release notes for more
information.

j

-----Original Message-----
From: perforce-user-bounces at perforce.com
[mailto:perforce-user-bounces at perforce.com] On Behalf Of Andres Fuentes
Sent: Wednesday, August 09, 2006 9:37 AM
To: perforce-user at perforce.com
Subject: [p4] Very big Perforce file : db.have
Importance: High

	Hello all,

recently I've changed our license file in the perforceroot folder, for that
I revised the rest of files and someones are very big...
Could be dangerous for our Perforce system that any db.* files has more than
2Gb size? 
I know that this is critical on NT, but could be dangerous on Linux to?
Exists any way to repare it?

Thanks in advance


A.F.