Wednesday, 15 August 2012

google app engine - How to migrate gae app to new config? -



google app engine - How to migrate gae app to new config? -

i'm updating webapp has been using default configuration. i'm starting utilize modules trying config

application: newkoolproject # other settings here... version: newkool runtime: python27 api_version: 1 threadsafe: true automatic_scaling: min_idle_instances: 5 max_idle_instances: automatic # default value min_pending_latency: automatic # default value max_pending_latency: 30ms max_concurrent_requests: 50

i pay instance hours, info reads , complex searches totalling few dollar daily on current budget (where limit 7 usd day avoid sudden spikes due dosing or other technical issue).

could feasible seek , squeeze app freetier using memcache , other technologies cut down costs? or should forget reaching free-tier (< 28 instances hours etc) , instead create configuration more optimal ux? how alter change costs?

update 141010 18:59 cet

i add together appstats

you'll need turn appestats on on local app engine development server, go through typical user flow. here instructions on how this: https://cloud.google.com/appengine/docs/python/tools/appstats

make sure turn calculate rpc costs on:

appstats_calc_rpc_costs = true

once go through typical user flow, go localhost:8080/_ah/stats , estimate how much specific calls , flows cost when production. great tool, helps identify bottlenecks , slow running areas within application.

google's recommendation not utilize memcache, split work smaller units (as much possible) leveraging task queues.

update: simple memcache usage example

my_results = memcache.get("some-key-for-this-item") if not my_results: #do work here memcache.set("some-key-for-this-item", my_results) homecoming my_results

google-app-engine python-2.7

No comments:

Post a Comment