[p4] Obliterate metrics

[Paul Goffin]

Obliterate is much faster if you can reduce the workload on the server by
not making it unwind branches.  In other words, obliterate the destination
of a branch or rename location before the source.

Sometimes it's easy to do this manually but a script that applies
"obliterate" to the section of the depot you want to remove "change by
change" and works BACKWARDS in time can do the job with no effort.

i.e. write a script that does the following:

Set counter to highest change number of interest.
Repeat
  p4 obliterate //path-to-be-removed/... at counter,counter
  decrement counter
Until counter = 0




-----Original Message-----
From: perforce-user-bounces at perforce.com
[mailto:perforce-user-bounces at perforce.com] On Behalf Of David Ferguson
Sent: 17 April 2007 07:42
To: perforce-user at perforce.com
Subject: [p4] Obliterate metrics


Okay, we split our depot into two last summer.  I'm finally getting around
to cleaning up all the old cruft that is now obsolete (since it was put into
the other depot)... Two choices: obliterate checkpoint surgery.
 
Surgery works, but support really seems to frown on it.
 
obliterate works ...  But wow it's slow.  Anybody got metrics on how slow?