优化Google App Engine的应用程序体系结构和实现

Question

It's my understanding that billing on GAE all boils down to instance-hours ("IH"), or how many server instances are running for some duration of time. However, it is obviously not that simple, because in addition to IH you quotas and resource limits that you must be leary of throughout the course of the day (since quotas replenish every 24 hours).

I am in the process of designing my first GWT/GAE app, and have come across many articles (some of which are cited below) where the authors talk about major refactorings they had to make to their code - post release - in order to help minimize billing and operational costs with Google.

In one instance, a developer implemented a set of optimizations to his GAE app which caused the same app to go from $7/day (~$220/month) down to $0 because it was finally under the "free" quotas and billing thresholds for resources.

Being so new to GAE, I'm wondering if there are any set of principles or practices I can incorporate into the architecture/design of my app upfront, that once trickled down into implemented, functional code and deployed to GAE, will cause the app to run as efficiently (monetarily-speaking) as possible.

Here are some deductions I've made so far:

• Maximize caching and minimize datastore hits
• Try to push as many asynchronous request handling to backend instances as possible
• Enable concurrent HTTP request handling so that the same instance can handle multiple requests at the same time

So my question: are any of these generalizations I've made incorrect, and if so, why (or are they conditional, where they hold true in some cases but not in others)? Am I missing anything critical here? For instance, how to determine what code belongs on a backend instance (where resource constraints are little more lax), making use of what kinds of GAE-specific profiling tools (AppStats, SpeedTracer, etc.) to see bottlenecks, etc.

Also, some cited articles:

• Configuring Max Idle and Minimum Latency
• GAE's own scaling best practices
• An example of CPU optimization

Answer 1

Based on experience, there are a huge laundry list of strategies for App Engine optimization, the applicability of which depends on the nature of your apps. Here are some more tips that I know of:

• For apps that serves a high amount of relatively static content, enabling the (as yet undocumented) edge caching could be a blessing to your weekly bills.

• Even with concurrent requests/threadsafe enabled, each frontend instances could only process 8 (for Python) to 10 (Java, Go) simultaneous incoming request before the scheduler decides to spin up a new instance for you.

• To counter the above restriction, I think there's a Google I/O video that recommends you to reduce the response time for any user-facing request going to the frontend instances to be ~100 ms.

• To the tune of the above strategy, if you have any task that requires a large amount of processing or datastore I/O, offload the task to the push task queue , and immediately respond the request. You can specify the target of the task queue , but for this purpose it does not need to be the backend, frontend instances are good enough, and offer infinite scalability.

• If you use the above strategy but still need to give the result of the processing or I/O to the user, use Channel API or any other messaging services to send the result back asynchronously.

• Task queues are amazing stuff to distribute the workload of your app. You could customize its behavior in detail , and they are invaluable in making sure your app scales nicely. You can even have a two-way communication between instances using both push and pull queues.

_{I'll add more points later on.}

Answer 2

Most of the time, cost optimizations will be specific to your app. Since you're asking about general principles, they mostly apply to CPU and datastore.

CPU:

Watch out about paying for a stalled CPU. If your CPU is stalled on a long operation (a slow datastore request, or a URL fetch, etc), App Engine may launch another instance, driving up your cost. There's a number of strategies for this - enable threading, task queues. I suspect when you talked about putting asynchronous requests on backends, it's to solve this problem as well. There's multiple ways to handle this.

Datastore:

1. Control your indexes carefully. Indexing contributes a lot to your costs.

2. Design your datstore carefully to minimize the number of requests you need.

3. Denormalize. Denormalizing is pretty standard procedure for NoSQL datastores. Essentially, it means store duplicate data in multiple entities when necessary. This saves $ on App Engine because you pay per request, but you don't pay on the size of the entity you return. For example, if you have Stores that sell Widgets, you may want to store a summarized version of all a single store's widgets inside the Store entity (provided it's expected to fit inside the 1MB entity limit). That way, when you display the store's page, you only fetch the one store entity, rather than the store entity plus every widget entity. Likewise, if you need to count the number of widgets, it's better to have that value inside the store entity than to issue queries to get the count.

Caching:

Caching saves you money on both the CPU and Datastore side. There's a pretty good video from Google IO: https://developers.google.com/events/io/sessions/gooio2012/310/