Hi Barry,
Thanks so much for the advice here. I think it helps me understand the
options a lot better. I've added PageSpeed as it seems like a good idea
generally. I've also added the below cache-control snippet. We'll see if
this works and if Google respects it. Hopefully it'll help.
<%
response.setHeader("Cache-Control", "max-age=600000, must-revalidate"); //
HTTP 1.1
%>
Thanks,
Phil
On Sat, Jun 29, 2013 at 12:45 PM, Barry Hunter <barrybhun...@gmail.com>wrote:
> If you set good Cache-Control headers, then you are allowing proxies to
> cache the file for you.
>
> Google sometimes (or least did) have a optimistic caching-proxy - you
> would often get that caching your pages (if the headers allowed it to!)
>
> But with PageSpeed, its more explicit, that will cache if you allow it to.
> So that's definitely an option.
>
> However there are many 'front end caches' (be it PageSpeed, or the other
> optimistic one) - so even though one caches it, you might still get
> requests from the other caches. So wont mean your server only generate it
> once per week, but it does mean it wont generate it for every request.
>
>
> But you also have MemCache at your disposal. Thats specificity designed as
> cache, and should work well in this situation.
> (you can also cache the file explicitly in the Datastore or Google
> Storage/Blobstore)
> so your instance can just fetch a regenerated file, rather generating it
> from scratch.
>
>
>
>
> On Sat, Jun 29, 2013 at 8:34 PM, Phil McDonnell <
> phil.a.mcdonn...@gmail.com> wrote:
>
>> I have certain pages (sitemaps, etc) that are very expensive for my site
>> to render. The underlying data changes often, but I could live with only
>> updating these pages once a week. Is there a way to configure app engine to
>> cache dynamic pages for long periods and not serve a new one? Would this be
>> effective given that server instances regularly turn over?
>>
>> I do not have PageSpeed service enabled although I could enable it. I am
>> on Java.
>>
>> Thanks,
>> Phil
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Google App Engine" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to google-appengine+unsubscr...@googlegroups.com.
>> To post to this group, send email to google-appengine@googlegroups.com.
>> Visit this group at http://groups.google.com/group/google-appengine.
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>>
>>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-appengine+unsubscr...@googlegroups.com.
> To post to this group, send email to google-appengine@googlegroups.com.
> Visit this group at http://groups.google.com/group/google-appengine.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>
--
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/groups/opt_out.
