Search code examples
performancegoogle-app-enginenamespacesquota

Using namespaces API for testing could affect performance and reliability of my Google App Engine application?

As asked here, I'm looking for a clean solution to setup a staging environment for my Google App Engine application.
Reading the new spec of Namespaces API, Google suggest that a possible use of this new feature is:

  • Creating Separate Datastore Instances for Testing and Production

In case I decide to use Namespaces for testing, could a stress test on Staging affect performance and reliability of my Production application?

Imagine a stress test that crawl and store a thousand of RSS feed in a FeedStored Model with transanctions on FeedStoreCounter and so on; could this activity on a staging namespace cause problem when the application try to do the same operation at the same time on the production namespace?
Also, do the different namespaces share the same quota?

Solution

  • All the data for all App Engine apps is stored in a single Bigtable. As such, data for different namespaces is just as distinct as data between different applications.

    If you're also using a separate app version to serve your staging app, the two versions will be running on different app servers, too, so traffic to one version won't affect the other versions.