Wow. OK, if it was happening to you with only 2 memcache set_multi_async calls, I'm generally doing over 200 in the course of 8 minutes or so, each with ~32 elements. I've added delays between them now, so it is now 300 over 15 minutes each with 20 elements.
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. Of course, that isn't a viable solution for everybody, and even now I'm thinking that I should test at 2 seconds to see what happens. 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). On Sunday, 25 August 2013 19:06:45 UTC+2, pdknsk wrote: > > PS. I should also add that I moved to a different app id. So this may or > may not also have helped fix it. > -- 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.
