How are you identifying that it's reloading? If the load is really light, the instance might just be timing out and getting killed before a 2nd request comes in.
On Sep 16, 4:55 am, Микола <[EMAIL PROTECTED]> wrote: > Yes, we have main() function. > > On 15 Вер, 22:56, Tony Arkles <[EMAIL PROTECTED]> wrote: > > > Do you have a main() function? > > >http://code.google.com/appengine/docs/python/appcaching.html > > > On Sep 15, 1:44 pm, "Myroslav Opyr" <[EMAIL PROTECTED]> wrote: > > > > Hi, > > > > thanks for hints. However while trying out complex app like rietveld, all > > > requests that happen to be close in time lands into same instance of app. > > > And it is quite strange for GAE to treat our application differently, and > > > reload it or spawn another instance of it. What is among criteria that > > > make > > > GAE to reload app or spawn separate instance? > > > > FYI, spawning an instance involves loading a bunch of modules that is > > > quite > > > slow in our case. We'd like to avoid extra instance reloads at any price, > > > i.e. we have application load request that is worth 24 regular requests > > > happening each 5th request! We'll be over CPU quota in no time. > > > > Load on application is minimal, i.e. it is being accessed only in test > > > purposes, thus "too many simultaneous requests" is quite not probable. > > > > We came to conclusion that it either segfaults or is being killed by GAE > > > for > > > some reason and restarted from scratch. What the reasons can be? Anybody > > > experienced similar behavior? > > > > Regards, > > > > m. > > > > 2008/9/15 Tom Kermode <[EMAIL PROTECTED]> > > > > > I believe you need to be prepared for GAE to have to load your > > > > application > > > > every single time someone requests any page on your website. Sometimes > > > > GAE > > > > will happen to have it cached, but this is not guaranteed. It might be > > > > that > > > > you hit a different machine in a different data centre with each > > > > request. > > > > > Rather than thinking about the app being run and subsequent requests > > > > going > > > > to the same instance until it stops running, you need to think of > > > > separate > > > > requests always going to a new instance, unless you're lucky and they > > > > happen > > > > to go to a cached one. > > > > > Cheers, > > > > Tom > > > > > 2008/9/15 Микола <[EMAIL PROTECTED]> > > > > >> Hi, > > > > >> I'm trying to run my application at GAE. At first request GAE loads it > > > >> to memory (creates instance). Subsequent requests goes to instance of > > > >> my application loaded to memory. But when there is five (more or less) > > > >> requests processed GAE reload my application. I know that there are > > > >> following reasons when GAE restarts applications: > > > >> * when an error occurred but at dashboard/Logs i don't see any errors > > > >> * if its average load is big (my app is 23.9 times over the average > > > >> request CPU limit, when it is being loaded) however subsequent > > > >> requests don't have warnings in log. > > > > >> Do anybody have any hints of why GAE reloads my application? Should I > > > >> submit this question as bug/issue in GAE Issue Tracker? > > > > >> Regards, > > > > >> crchemist. > > > > >> P.S. Sorry for repost. > > > > -- > > > ..................................................................................................... > > > Myroslav Opyr ▪ CTO ▪ Quintagroup ▪ http://quintagroup.com > > > ˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙ > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
