Hmm, from what I understand it would be possible to keep one instance. Thats all Free apps get anyway.
I've setup against an app not currently serving other traffic two cronjobs, on a server here. every 5 minutes, hits a URL (thats your kiosk) - and then once an hour runs " ab -n 30 -c 2 -t 15 http://....appspot.com/..."; to similuate a user. Have also set minumum maximum idle instances (1) and max pending latency. So far it has only one instance. Even when requests reached 4 rps. Another idea, you get 9 hours of backend free a day too. Could you shunt the 'users' to actully be done via your backend. Leaving the single frontend instance to serve kiosk traffic? On Fri, Sep 2, 2011 at 4:31 PM, Joshua Smith <[email protected]>wrote: > > On Sep 2, 2011, at 11:10 AM, Barry Hunter wrote: > > Dont you get one instance (well two until multi-threading) free? - so > you can have a dynamic instance always loaded. (ie you get 24 instance > hours free a day) > > > You don't get 2 until multi-threading. You get one. They are just > reducing the price of the second one. > > And under the new system any $ > 0 = $108 / year > > Hey google overlords: How about instead of charging half for the pre-2.7 > period, you bump the free quota to 48 hours until 2.7 comes out? I bet that > will eliminate a lot of the kvetching here from the used-to-be-free crowd. > (And charging half until November didn't seem to ameliorate the angst of > the $Ks/mo crowd anyway.) > > > So providing what you want can be served by this instance, you dont > have any (instance) changes. > > > If two users happen to hit the site at around the same time, I'm pretty > much guaranteed to get > 1 instance. With one running 24/7, there is no > room to handle this bump. > > (Plus, there are the scheduler bugs everyone is reporting, which drive up > the instance count even more.) > > > As for saving the file, you could put it in the blobstore. The handler > to serves the send_blob should be very quick and not tie up the > instance for long. > > > How long doesn't matter. I need the instance to be untouched by the > kiosks, to avoid the 24/7 life thing. > > > Or Google Storage for developers (G's answer to S3) - that avoids the > instance totally. > > > I'll have to look into that. I have a lot more experience with S3, but if > there is a nice GAE/GS bridge, perhaps that would work for me... > > You might have to optimize the code around user-interaction requests, > to make sure again they stay on the single instance. But set a high > minimum latency, and that shouldnt be an issue > > > (or i've missed something) > > > I don't think it's really possible to get GAE to only serve with one > instance. It's just not in the nature of the scheduler algorithm. > > And in my case, I really don't need it to. Here are the stats for the most > recent month (only counting humans): > > > That should easily fit under the quotas, even if it has to spin up a bunch > of instances for each human. > > But only if I get the Kiosks to stop burning all my quota. > > I'll look into GS for Developers… > > -Joshua > > -- > 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. > -- 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.
<<PastedGraphic-7.png>>
