On Mon, Feb 20, 2012 at 5:33 AM, Johan Euphrosine <[email protected]> wrote:
> On Mon, Feb 20, 2012 at 11:25 AM, Andrin von Rechenberg < > [email protected]> wrote: > >> I guess that's the same solution as just deploying two different >> versions. A threadsafe one and a non threadsafe one. Or did >> I misunderstand you? >> > > appcfg.py provide commands to help you manage your backends deployment and > configuration, with `backends.yaml` and `appcfg backends update`. > > That make the solution more convenient than using multiple versions on > frontend instances. > This adds the significant downside of no auto-scaling. I don't see how that's more convenient :-) Andrin: In javaland I would simply synchronize the people-search function so that at most one thread can execute that routine in a single instance at once. It means all people-search requests in that instance will queue up in serial, which could cause undesirable waits if the function takes significant time, but if the requests are spread out among enough instances it probably won't be an issue. I don't know what the python equivalent of 'synchronized' is. Jeff -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. 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.
