> > The edge cache is just that - a cache. It doesn't guarantee that no 304 > > requests will reach your app, only that they will be satisfied by the cache > > if possible - and if the headers you set permit it. The more popular your > > content is, the more effect you're likely to see from the cache. > > Thanks, Nick. I've used Squid and Varnish a bunch, so I'm familiar with > caching. This is the first I've heard that GAE's edge cache only kicks in > for dynamic content if it surpasses a certain request threshold. Based on > what others have written, I'd understood that enabling billing makes the > cache kick in regardless of popularity. Good to know the true story. >
Joshua, I think Nick meant that popular content is less likely to be evicted from the cache, not that it is only cached if it is popular. The onus is always on you to have as many levels of cache in place as you can get away with so, depending on what you are caching, you are going to benefit from using the edge cache, memcache, and instance global variable caching all at the same time. You can't trust that memcache will always have your data either and that is not just because it has downtime occasionally, it also has rules that allow it to evict data. - Bryce -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
