It's not a 1 second limitation. But if you hammer with concurrent transactions on a single entity group you get a lot of "collisions" and retries and that slows the whole process down. A rule of thumb is don't try to update a single entity group more then once a second for a long period of time. It's not about the kind but the individual instances of a kind. If you have 50 request/s and they all want to update 50 different objects with transactions it should work. It might slow down a bit if they all hit the same tablet server but you won't have collisions
The example at the TaskQueue man page also mentions the 1/s update by transaction. 2010/6/24 dflorey <[email protected]>: > Back to my initial question... ;-) > @djidjadji: Thanks for your post! Do you know more about this "1 > second limitiaon"? > I'm working only on separate entity groups (but they are of the same > kind) only. > I've been in that talk at the Google IO but I'm still confused why I'm > not able to execute more than ~2 tasks per second. > Is there some global transaction/s limit per app? > Or is the problem just that my app has low traffic for a long time and > then I'm starting ~1500 concurrent tasks? > But doing this for some time, I do not get any warnings about new > allocated nodes, but it is still not getting faster. -- 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.
