[p4] Managing diskspace usage of Perforce Proxy

[Frank Compagner]

I've spoken to support about this, and their stance is that it is a
good thing p4 stops working when the proxy cache is full. That way
users will complain (rather loudly, in our case), and somebody will
need to clean the cache right away. If it were to continue working
with just some warnings the cache might never be cleaned and
performance would deteriorate.

I don't think I agree with this position, but I do see their point. By
far the best way to solve all this is if p4p would do the cache-ageing
itself, perhaps through an extra commandline parameter specifying the
maximum diskspace the cache can use. Support tells me this is an
outstanding feature request, but no idea if/when this might appear.

In the mean-time, I do now have a proxy_clean python script running on
a couple of our proxy's (both windows and linux), if it runs well for
a few more days I'll put it in the public depot.

----------------------------------------------------------------
Frank Compagner                                  Guerrilla Games

pg> Quoting Frank Compagner <frank.compagner at guerrilla-games.com>:

>> But the main point is that a proxy server should be almost completely
>> maintenace free. In the current situation, if the admin forgets to
>> check the proxy regularly (happened once or twice), the proxy fills up,
>> and perforce stops working for the users on that proxy. This is just
>> stupid, and I want something more low maintenance.

pg> I agree.  Have you reported this to Perforce as a Bug?

pg> I can see implementing cache-ageing features on the proxy would be a big
pg> overhead for it, but if the cache is full the proxy should fall back to working
pg> as a relay.  It shouldn't stop working completely!