task queue. why? that would be overcomplicated.
On Wednesday, January 16, 2013 2:44:43 PM UTC-5, Jesse wrote: > > I never use get_serving_url on user-facing requests--it's slow and it > sometimes craps out and needs a retry. Use it a task queue once and save > the resulting URL onto your model. Then just manipulate the URL as needed > (a property would make this uber simple). > > > On Wednesday, January 16, 2013 11:34:15 AM UTC-6, Joker321 wrote: >> >> Latency for my application seems to be very high even though I've >> optimized it significantly. >> >> Here is an appstats sample for one of the requests: >> >> (4) 2013-01-16 08:33:19.750 "GET /" 200 real=3154ms api=0ms overhead=12ms >> (39 RPCs, cost=0, billed_ops=[]) >> images.GetUrlBase 18 0 >> memcache.Get 10 0 >> datastore_v3.Get 9 0 >> datastore_v3.RunQuery 1 0 >> user.CreateLogoutURL 1 0 >> >> Seems images.GetUrlBase is one of the main culprit as well as memcache >> (?). Currently I have blob being fetched and passed to get_serving_url, >> with variable image sizes throughout the application. >> >> Any recommendation on performance improvements? thanks >> >> -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/BoVuUu6oV3YJ. 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.
