I suppose that the prospect of it not sucking and not reaching the 2 million is what I have in mind... more like 1000 if I am lucky ( that would probably fall in the sucking category for you I suppose... ) but you are right, if a new instance is created it is an issue... I have done a stress test of calls every .1 of a second and it did not create new instances, and I think that even with more that a 1000 users if wont create a new instance... ( if the app did not 'suck' in the end and I was to get an exponatial number of users per day I woud update the service )
but in regards to my question about kipping the instance alive with a cronJob is this possible... I would like to use the conJob to keep the instance alive and to commit the in-memory values to bigTable its just that reading and writing from bigTable every time gets me around 200 users ( so thats 170$ in my poket and now I have to pay for the service.... ) Thank you for your post :) -- 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/-/o_dXNqLF1Y4J. 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.
