I (and many others I think) have been frustrated with how instance hours billing can explode in the face of traffic spikes. I've submitted Issue 5858 <http://code.google.com/p/googleappengine/issues/detail?id=5858> to help us put a hard limit on that scaling out. Regardless, it is quite clear that the only real hope is to implement multi-threaded request handling. Java has that option and the new Pytohn 2.7 runtime is supposed to bring that. Seeing how important concurrent handling is going to be to keeping bills reasonable, it's a real shame that the Python's New-GIL improved concurrency<http://docs.python.org/dev/py3k/whatsnew/3.2.html#multi-threading> was rejected for Python 2.7 in part to keep encouraging adoption of 3.X.
-- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/qui7GhQvcCcJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
