At a peak, a user of my application can make around 30,000 - 50,000 requests a day that returns some xml data. The xml data itself is cached so the request is only doing two RPC calls (one for authentication, one for the xml string). However, this seems to use a lot of CPU time and outgoing bandwidth. I've tried using memcache for the xml data but it turns out that it is usually a low hit ratio so it is quite a bit slower. Is there any form of aggressive caching or method I can use to limit the resources used over millions of requests per day?
P.S. I have looked at this article http://www.kyle-jensen.com/proxy-caching-on-google-appengine and figured that it would not work well in my scenario because I want to be able to authenticate on each request. Thanks, Ricky Button -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
