The memory issue is indeed tangental to the scheduler issues. A few of us just happened to notice it from de Witte's instance snapshot and figured we'd point it out as a separate issue and potential problem for him once the 128MB limit is enforced.
I believe that that instance would already be killed off prematurely in the backend with an OutOfMemoryError. And will be in the frontend as well at some point (soon?). /Tom On Sep 2, 5:57 am, Bay <[email protected]> wrote: > This has nothing to do with memory leaks. As I told before I experience the > exact same problem and > 1) the new limits are not in force yet > 2) there are no mentions in the log that a soft memory limit has been > reached (which there are, if you have a leak and it closes down instances as > a consequence) > 3) settings about max. idle instances and latency before new instance is > spawned are already set to a configuration that should produce the least > amount of instances > > I ask you please try not to derail the discussion from the fact that the > scheduler is broken and needs > 1) a quick fix in the form of a user-setting to allow only 1 instance being > run (as the needless and passive instances spawned are costing a lot of > money under the new regime for small apps) > 2) a long-term fix so that it does not produce new instances that go around > doing nothing (this should help larger apps as well) -- 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.
