5 ms·
I don't like it in theory either, but you can write a dummy cron job. It is wasteful in the sense that their system relies on 'garbage collecting' dormant apps.
by mbenjaminsmith 16y ago
I don't like it in theory either, but you can write a dummy cron job. It is wasteful in the sense that their system relies on 'garbage collecting' dormant apps. But it's not something you're going to see hike your monthly bill.
The initial load is slow. I can't remember the average wait but it does add on several seconds to a pageload. Given that 1/n users will deal with it, it's probably not an issue, but it did always bother me.
In general the overall performance has degraded in the last couple of months. I only use it as a hackish-CDN at the moment but I have seen deploys timeout up to 10 minutes. I guess the datastore is dealing with some serious growing pains as well.
- Tichy 16y agoThanks for the info. I have considered giving it another shot, but I guess I'll wait for the reserved instances at least. With the 1/n-th visitor: would be especially annoying if it happens to be the Google crawler und the site tanks in the rankings because of slow load times.
- mbenjaminsmith 16y agoI hadn't thought of that. I wonder if Google Seach and Google App Engine ever discuss slow loading times. Depending on what you're looking for, I would probably steer you away from App Engine. I don't have time to go into details, but I really think the cons outweigh the pros. I moved a while ago from AE to regular Django and I spend a lot less time coding. You've got plenty of other options for similar cost/scalability as well.
- Tichy 16y agoI guess for most cases it is too special, but I have an old Java app that doesn't even need a database, so I thought that might run well without too much effort.
- mbenjaminsmith 16y agoThat's exactly right. There are a handful of cases where it's a great fit and should be taken advantage of.