[p4] Deleted branches affecting the Perforce performance

Webmaster33 webmaster33 at gmail.com
Sat May 27 05:06:15 PDT 2006


> The "p4 obliterate" has now very high performance and you can use it for
> database cleanup whenever you want (in 2004.2 and elder versions the p4

p4 obliterate was not useful in my case.
Perhaps I did something wrong, but I was not able to 
remove the files from internal db.

Does p4 obliterate work in the case, when the files are
not available in the depot, but still are available in the 
internal db?

This is my case, and it seems p4 obliterate was not able
to solve such case.


I did something wrong?


Regards,
Webmaster33


*********** REPLY SEPARATOR  ***********
On 2006.05.27. at 11:56 Sheizaf, Yariv wrote:

> HI Baz,
> 
> If you refer to "destroy branches that are not in use anymore, there is
> a very good improvement in v2005.1 and on:
> The "p4 obliterate" has now very high performance and you can use it for
> database cleanup whenever you want (in 2004.2 and elder versions the p4
> obliterate usage was so slow that using it was possible only on weekends
> shutdown time or alike).
> 
> Regards,
> 
> Yariv Sheizaf
> bmc software
> Identity Management BU
> Configuration Manager
> Office:  +972-3-6451-281
> 
> _______________________________________________
> perforce-user mailing list  -  perforce-user at perforce.com
> http://maillist.perforce.com/mailman/listinfo/perforce-user

*********** END REPLIED MESSAGE  ***********



More information about the perforce-user mailing list