[p4] Proxy disk usage

[Sweeney, Tony]

Short answer: no.

The RCS files in the backend compactly contain all revisions of each
text file.  In the proxy cache, each version of the file requested is
materialized separately.  Also, in the server, branches, at least
initially, share a single lazy copy of the parent file.  In the proxy,
these files are again materialized separately in each branch.  Binary
files are compressed by default in the server.  I don't know that this
is true (or not) in the proxy cache.  Clearly proxy sizings will depend
on use patterns, but in a pathological case, could greatly exceed the
size of the main depot.

Tony.

quis custodiet ipsos custodes -- Juvenal VI, 347-8 

> -----Original Message-----
> From: perforce-user-bounces at perforce.com [mailto:perforce-user-
> bounces at perforce.com] On Behalf Of Chris Weiss
> Sent: 01 June 2006 23:44
> To: Perforce Users
> Subject: [p4] Proxy disk usage
> 
> The System Administration Guide states:
> "P4P caches file revisions in its cache directory. These revisions
> accumulate until you delete
> them. P4P does not delete its cached files or otherwise manage its
> consumption of disk
> space."
> Then:
> "Warning! If you do not delete cached files, you will eventually run
> out of disk space."
> 
> If the Proxy is just caching the files and their revisions, is it safe
> to say that (except for the logfile and results of any Obliterate
> commands) the cache will not exceed the size of the original depot?
> 
> --
> -Chris
> _______________________________________________
> perforce-user mailing list  -  perforce-user at perforce.com
> http://maillist.perforce.com/mailman/listinfo/perforce-user