[p4] Very big Perforce file : db.have
Andres Fuentes
andres.fuentes at altana.es
Thu Aug 10 01:27:44 PDT 2006
Hello all,
thank you very much for yours opinions.
Best Regards,
A.F.
-----Mensaje original-----
De: Todd Short (tshort) [mailto:tshort at cisco.com]
Enviado el: jueves, 10 de agosto de 2006 1:33
Para: David Ferguson; jgrills at junctionpoint.com; Andres Fuentes;
perforce-user at perforce.com
Asunto: RE: [p4] Very big Perforce file : db.have
Ours isn't very big, but we whack client's that haven't been used for
over a year to clean it up a bit. Those with clients unused for 6 months
are requested to clean them up.
--
-Todd Short
// tshort at cisco.com
// "One if by land, two if by sea, three if by the Internet."
> -----Original Message-----
> From: perforce-user-bounces at perforce.com
> [mailto:perforce-user-bounces at perforce.com] On Behalf Of
> David Ferguson
> Sent: Wednesday, August 09, 2006 5:04 PM
> To: jgrills at junctionpoint.com; Andres Fuentes;
> perforce-user at perforce.com
> Subject: Re: [p4] Very big Perforce file : db.have
>
> Ours was over 55G before we did some repository splitting and
> were able to
> reduce it to 30G (on one server, the other is around 20G).
> We rebuild the DB
> approximately every 2 months and usually regain about 10-15%...
>
> -daf
>
>
> -----Original Message-----
> From: perforce-user-bounces at perforce.com
> [mailto:perforce-user-bounces at perforce.com] On Behalf Of Jeff Grills
> Sent: Wednesday, August 09, 2006 9:04 AM
> To: 'Andres Fuentes'; perforce-user at perforce.com
> Subject: Re: [p4] Very big Perforce file : db.have
>
>
> 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_perf
> tune.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.
> _______________________________________________
> perforce-user mailing list - perforce-user at perforce.com
> http://maillist.perforce.com/mailman/listinfo/perforce-user
>
> _______________________________________________
> perforce-user mailing list - perforce-user at perforce.com
> http://maillist.perforce.com/mailman/listinfo/perforce-user
>
More information about the perforce-user
mailing list