Yes, maybe you are right.
On Sep 17, 4:18 pm, Wooble <[EMAIL PROTECTED]> wrote:
> On Sep 17, 6:04 am, Микола <[EMAIL PROTECTED]> wrote:
>
> > >I would first try to find a way to avoid loading the 12MB because you
> > >can't rely on it staying in memory between requests.
>
> > Yes, but the question is - why GAE reloads application without any
> > warnings, when application don't use many resourses, and why at the
> > same time it don't reloadhttp://codereview.appspot.com/(seeat left
> > top corner)? Its look like segmentation falt at GAE or something like
> > that.
>
> There's absolutely no reason for you to expect all of your requests to
> be served by the same server, or for a server to keep your enormous
> application in memory if it's not getting a lot of requests; that
> memory can be used to hold lots of little applications instead. I'm
> not sure why you assume that there must be a segmentation fault; GAE
> isn't *designed* to automatically keep an application in memory until
> it crashes, it's designed to cache whatever applications its algorithm
> thinks it should cache to give the best possible performance to
> everyone.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
