ClientCache and Large Files
Hello, We're running ZEO with Zope 2.5.1. We currently have a ZEO Cache (ClientCache) of 200 meg. Occasionally someone will download a 300 meg file that completely blows away the client cache. Is there a way to prevent this? Thanks, -Brian Brinegar ECN Purdue University
We're running ZEO with Zope 2.5.1. We currently have a ZEO Cache (ClientCache) of 200 meg. Occasionally someone will download a 300 meg file that completely blows away the client cache. Is there a way to prevent this?
I'm afraid not; this isn't a very typical use case. You could implement a file size limit, or increase the cache size to be more than twice the largest expected dowload (the cache is implemented as two files, each of which is limited to half the nominal cache size). --Guido van Rossum (home page: http://www.python.org/~guido/)
On Monday 16 December 2002 10:53 am, Guido van Rossum wrote:
We're running ZEO with Zope 2.5.1. We currently have a ZEO Cache (ClientCache) of 200 meg. Occasionally someone will download a 300 meg file that completely blows away the client cache. Is there a way to prevent this?
You're best bet would be to put a proxy cache in front of Zope. Zope's not very efficient at serving big static files like this compared to Apache or squid.
I'm afraid not; this isn't a very typical use case. You could implement a file size limit, or increase the cache size to be more than twice the largest expected dowload (the cache is implemented as two files, each of which is limited to half the nominal cache size).
I think it would be nice to be able to control cacheability of certain objects. However it smells like a YAGNI, especially with good front end caches that can take care of it. -Casey
participants (3)
-
Brian R Brinegar -
Casey Duncan -
Guido van Rossum