Hi Tim, Yes it's cool, really. The reason I segment the sqlite guestbook into a single instance is that there is no easy way to share the sqlite table on the local disks between the instances. We run a multi-threaded server on each instance. If you set threadsafe:true in the app.yaml file, the actual server will run in the muti-threaded mode, so it can handle concurrent requests.
-- Takashi On Fri, Jun 21, 2013 at 12:45 AM, timh <[email protected]> wrote: > Thats pretty cool. > > Just looked at the SQlite example for backend VM on python. It raises an > obvious question, what app server runtime are you running on the vm backend > to support a deployed python app. > Is it the new dev_appserver or something else ? What sort of concurrency > does it support ? > I note in the document the getting started guide all requests pass > straight through to the backend, and there for concurrency has to be > managed on the vm. How would someone approach this ? > > Thanks > > Tim > > > On Friday, June 21, 2013 3:21:06 AM UTC+8, Takashi Matsuo (Google) wrote: > >> >> Fellow App Engine Gurus, >> >> We're happy to announce the next generation of App Engine Managed >> Backends. These Backends utilize the App Engine VM Runtime, allowing >> developers to run Backends on Compute Engine VMs. By building on top of >> Compute Engine VMs, developers can: >> >> >> - take advantage of higher CPU and memory >> - rely on longer-lived processes >> - utilize a local filesystem >> - communicate via native network stacks >> - execute external processes >> - access the entire JRE >> - upload arbitrary Python extensions >> >> >> Given that these are App Engine Backends, you can still use all the App >> Engine APIs to access the existing managed services (Datastore, Task >> Queues, Memcache, etc.) >> >> Updating existing Backends to run on Compute Engine VMs is a simple >> config change: >> >> app.yaml >> -------- >> application: app-id >> version: v1 >> runtime: python27 >> *vm: true* >> * >> * >> *manual_scaling:* >> * instances: 1* >> >> >> That’s all you need to get started. We’ll pick a deafult VM machine type >> and spin everything up your behalf. Of course there other options that you >> can set (including machine type) and these are documented in the Getting >> Started >> Guide<https://docs.google.com/document/d/1VH1oVarfKILAF_TfvETtPPE3TFzIuWqsa22PtkRkgJ4/edit#> >> . >> >> In order to build a great product, we need quality feedback from brave >> early adopters. If you’re interested test driving, please sign-up at the >> link below and we’ll take care of the rest. >> >> App Engine VM-based VM Runtime - Trusted Tester >> Sign-up<https://docs.google.com/forms/d/1NTPROehZLn7lzu3pcXryB8BlZN5cu0SwiIzPnl35xHs/viewform> >> >> Also, if you have any questions, please feel free to send an email to: >> appengine-...@**googelgroups.com >> >> Thanks! >> >> -- >> Takashi Matsuo | Developers Programs Engineer | [email protected] >> > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/google-appengine. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- Takashi Matsuo | Developers Programs Engineer | [email protected] -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-appengine. For more options, visit https://groups.google.com/groups/opt_out.
