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 means you can have a task/cron periodically rebuild the sitemap whenever you want, - have the task render it and store it in the datastore, invalidate memcache and the next time it is fetched - updated sitemap. T On Sunday, June 30, 2013 3:34:31 AM UTC+8, Phil 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.
