On Tue, Aug 27, 2013 at 1:14 PM, Julian Kent <[email protected]> wrote:
> Vinny, I haven't hit the error again since I changed to batches of 20 per > set_multi_async and added 5 seconds delay between each write. > Terrific. I love happy endings :-) On Tue, Aug 27, 2013 at 1:14 PM, Julian Kent <[email protected]> wrote: > now I'm thinking that I should test at 2 seconds to see what happens. > That's a good idea. There's really no hard and fast time delay rule here, use whatever delay that keeps your application running. The only thing I would suggest is to slowly and incrementally lower the time delay; i.e. one day use a delay of 4.5 seconds, then the next day delay by 4 seconds, and keep lowering until you hit errors. On Tue, Aug 27, 2013 at 1:14 PM, Julian Kent <[email protected]> wrote: > Also, I thought the whole point of the async calls was that you could just > dump and forget while you keep on processing. If you have to wait before > you can dump more it really doesn't add much value to them. Thinking I > might switch back to regular set_multi calls (and yes, I was hitting the > error with them as well). > > That's correct, for the most part. Yes, async calls are "dump and forget" but there are limitations to how many async operations can run simultaneously, not to mention limitations on bandwidth (moving data around memcache, etc). Play around with how many async operations and how much data you can write to memcache before incurring errors. ----------------- -Vinny P Technology & Media Advisor Chicago, IL App Engine Code Samples: http://www.learntogoogleit.com -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-appengine. For more options, visit https://groups.google.com/groups/opt_out.
