On Mon, Jul 1, 2013 at 7:02 PM, Phil McDonnell
phil.a.mcdonn...@gmail.comwrote:
In implementing PageSpeed I saw my overall reads go way up (~double),
which from a cost perspective is counter productive for me. Graph attached.
Does it make sense that we're seeing less caching with PageSpeed
they don't support the Vary header. :)
On Sun, Jun 30, 2013 at 3:18 PM, Barry Hunter barrybhun...@gmail.comwrote:
On Sun, Jun 30, 2013 at 9:08 PM, Rafael mufumb...@gmail.com wrote:
This is a very common problem for me.
I was super used to varnish on normal servers. With appengine it's
You can always use the datastore as another level of cache. Process the
sitemap, store its rendered output as a record in the datastore, and in
memcache.
If memcache fails do get() to fetch the rendered output from the datastore,
which will still be heaps faster than re-building it.
It also
This is a very common problem for me.
I was super used to varnish on normal servers. With appengine it's very
hard because the page will never be as fast as varnish if you use memcache.
I tried emulating a reverse proxy with cloudfront, but they don't cache
HTML. The problem here is very simple:
On Sun, Jun 30, 2013 at 9:08 PM, Rafael mufumb...@gmail.com wrote:
This is a very common problem for me.
I was super used to varnish on normal servers. With appengine it's very
hard because the page will never be as fast as varnish if you use memcache.
I tried emulating a reverse proxy with
