laterGet and laterPut about goon HOT 5 CLOSED

I don't think so. As I understand it, all appengine/delay does is to create a task in the task queue to do the operation you delayed. Which means that instead of sending your put/get data to the datastore, you're sending it to the task queue (which then sends it to the datastore and masks/hides your errors).

Tasks Queues are good for longer running operations or operations that have to deal with an external API (which may not respond as quickly). The (correct) assumption that is made in the presentation is that sending an e-mail is a slower task than creating the task request to send the email.

from goon.

I was going to paste some stats showing that puts were ten times slower than a task add, then I realised the put stats in question were from 2009 ;)

from goon.

Hey, great site! I'm not sure I've seen that before.

So on a "simple" put, it looks like adding to the taskQueue would take ~12.5ms and a datastore put would be ~9ms. So I'm standing by my assertion ;)

from goon.

You are exactly right.

from goon.

Off-topic comment.

@mzimmerman That status site isn't as great as it may seem. It has a reputation for showing all green when a whole datacenter of GAE is down. The main issue seems to be that it generates its status reports from a single app on a single datacenter, which probably runs on a single machine, and thus is in no way representative of the aggregate performance of GAE. The site used to be the punchline to jokes during downtime in the early beta days, so take that data with a few grains of salt.

from goon.