Thanks I'll check this out. Is there anything I can to do optimize
bandwidth used. Each of those 50,000 requests are completely different
entities and have different uris, (/api/articles/46452)

On May 13, 10:10 pm, Gopal Patel <[email protected]> wrote:
> you can use in-instance caching. It may not be always up to date but will
> give you extreme speeds.
>
> http://appengine-cookbook.appspot.com/recipe/decorator-to-getset-from...
>
> checkout fifth one.
>
>
>
> On Sat, May 14, 2011 at 4:37 AM, Ricky Button <[email protected]> wrote:
> > 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 [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.

-- 
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.

Reply via email to