I'm currently using the pull queue with tags, and have experienced
TranscientError in the past.
Thanks to support cases still being there I can go back in time with
precise figures :)
Here are my usage figures if it can help:
Currently:
Daily average 7-8 tasks/second enqueued over 2 tags,
I forgot to mention - but you may realize if you do the math - the figures
about when I split to 20 task queues were obtained while testing with
traffic split, so it did not get the whole 1,800req/sec traffic but a
subset of it.
--
You received this message because you are subscribed to the
Thanks so much, the information is extremely useful
I was unsure about the need for multiple pull queues, but it seems to be a
must. I do use the method for regular queues, where the limits are clear
On Wednesday, March 12, 2014 10:27:23 PM UTC+2, Alexis wrote:
I forgot to mention - but you
I've checked the performance of my datastore based task pipeline, the
performance seems to be very poor, there are many missed/old tasks (db
entities) - probably caused by query delays - as I query for tasks, and the
delay should be ~30 seconds at most for the system to work, doesn't seem to
