Are you using JDO by any chance de Witte? There is a bad connection leak in DataNucleus (OMFContext) that results in major leaked memory. If you have non-transactional reads enabled in jdoconfig.xml (the default) you have this leak.
Event when the request limit was only 15000, my instances grew their whole life up (on every read) to about ~130MB by the 15000 requests (and would have kept growing) After changing to: <property name="javax.jdo.option.NontransactionalRead" value="false" / > and wrapping all reads (including queries) in transactions, my instances hang steady at ~80-90MB. I'll keep it his way until the problem is fixed. I found the leak when profiling with JProfiler, and then noticed there was an old issue raised by the datastore guys on it that was since closed pending an eventual upgrade to Datanucleus 3.0. Can't seem to find the issue right now though. /Tom On Sep 2, 5:16 am, de Witte <[email protected]> wrote: > The app itself doesn't need much memory. The memory footprint is high > because of the many active threads to handle the requests. > > Less memory > means lesser threads > means lesser requests to be handled > asynchronously by a single instance. > > So hopefully they won't reduce it, where did you read it? -- 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.
