Interesting, thanks for the link The app I mentioned used db, my new app uses ndb tho I don't experience memory issues frequently with it
The app that experiences memory leaks has crons that pulls and processes 40 entities at a time, entities are <1MB, so when instances are flooded with these crons, memory issues occur frequently Interestingly, if the routine is slow, they occur less, but if the routine is fast, it occurs every 30-40 requests On Friday, January 15, 2016 at 9:42:23 PM UTC+2, Christian F. Howes wrote: > > FYI, if you use NDB there is a memory leak: > https://code.google.com/p/googleappengine/issues/detail?id=9610 the > google folks are having trouble pinning it down, but it's there. i just > let my instances restart as they run out of memory as i have not been able > to find my other memory leaks (i'm sure i have more then just the NDB leak). > > On Friday, January 15, 2016 at 9:50:24 AM UTC-8, Kaan Soral wrote: >> >> I have an app that kills instances after just 30 requests sometimes, it >> functions perfectly tho, the instances die pretty gracefully, my assumption >> is that they don't take anything with them, rather handle all their >> requests and die after that >> >> I don't upgrade to F2 as it increases the costs significantly, it's >> harder to utilise F2 instances efficiently >> >> My .02 >> > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at https://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/1e2b4cf4-ae21-48c0-8698-43925d68a380%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
