Glad you have met with success. I have also been using pull queues with task tags as counters and for other aggregating behavior as well. I have also enjoyed success with this approach. For simple write heavy counters, I think I *may* prefer the good old sharded counter. There are plenty of use cases where pull queues with tagging are an excellent solution.
On Sunday, March 15, 2015 at 4:21:06 PM UTC-5, Kaan Soral wrote: > > Well I went ahead and utilized the pull queues > > Replaced my existing taskqueue/db routine that I stress tested here: > https://groups.google.com/forum/#!topic/google-appengine/qxQZJGHd8c4 > > I have to say I love pull queues, out of 1M separate increment tasks, the > total result was 1M+25, the error is +~0.00-ish, which I consider > acceptable (it might have a separate cause, yet there was a single > .delete_tasks exception that might be the cause, unimportant) > > Some pro's: > > - Didn't notice any chronic put or pull exceptions > - Pull's are chronological, at least in my limited trials they were > 100% chronological, they should be (are they chronological as a feature?) > - Arbitrary tags seem to work > - The put and pull performance is very very satisfying, you can > repeatedly pull and delete 500 entities for example, from a single tag > > If anyone from google reads this, please kiss whoever implemented/designed > pull queues for me > > I really wish all of the services were this robust, I hope it always > continues like this > -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/7ca66f70-5c45-4541-8f94-72ea541d4dd7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
