"Kearney, Greg" <GKearney at maxis.com> wrote:
Do you really have 50GB of data which change from one version to the next?
Depends what you call a version. Generally, over the life of the project the
data will migrate in much the same manner as source code does. An average is
probably ~4 revisions; however, other files may get 10s of revisions.
...
But even with this model eventually the disk space will run out.
Several people have gotten back suggesting removing the .gz files for the
back revs. This seems like a reasonable work around. So will probably do a
veriation off of this.
But, Perforce's binary file storage can already do compression. I don't know
if the compression is smart enough to avoid storing something compressed if
the compression process makes the file bigger. Check out this
command:
p4 help filetypes
for a description of the different file types. Also...I would GUESS
that you could delete the individual files out the server's depot
directory tree. Binary files are stored one file per revision, I
believe. I doubt that it would hurt anything (aside from your ability
to retrieve those revisions) to just delete the revisions you know you
don't need any more. But...I've never done that, standard disclaimers
applied, it's your foot and your gun if you hit your foot...:-)).
6 messages in com.perforce.perforce-user[p4] Re: Large amounts of Binary data...