Live data from Hacker News

The Unofficial Guide to Migrating Off of Google App Engine

www-cs-students.stanford.edu

61–63 of 63 posts

Re: The Unofficial Guide to Migrating Off of Google App Engine

#61
post #35

Earlier quoted context omitted.

I wrote my own. http://github.com/thurn/ackbar . If an article gets popular, I've paid up to $5, but below 6000 hits, it's all free. Latency could be better, but there's a lot of factors there (Clojure might be one of them?).

I see, thanks. If you don't mind, how come you pay? The free tier seems very large for a simple blog, which resource did you run out of?

Bandwidth runs out fast (images are the killer). CPU has gone over a couple times too.

Re: The Unofficial Guide to Migrating Off of Google App Engine

#62
post #54

Earlier quoted context omitted.

Oh wow, that's surprising and somewhat disconcerting. Do you have any sort of reference? If true, it's very serious.

I have no exact data at the moment. I looked through my application's logs and compared the response times in situations when the front page loads from a full-page cache entry and when it has to build the page from multiple pieces of memcached data. If I find time, I'll write a small benchmark application which tests memcache performance. Empirically however, App Engine's "memcache" is pretty slow.

Using appstats, you should be able to get this information without having to write your own profiling.

Re: The Unofficial Guide to Migrating Off of Google App Engine

#63
post #61

Earlier quoted context omitted.

I see, thanks. If you don't mind, how come you pay? The free tier seems very large for a simple blog, which resource did you run out of?

Bandwidth runs out fast (images are the killer). CPU has gone over a couple times too.

I take it that your images are rather static. If so, you should be adding caching headers which will cache them for free in Google's front end servers.
Post reply on HN