This issue has been open for about a year: http://code.google.com/p/googleappengine/issues/detail?id=1646
Also, appstats is showing total CPU usage, not total memory usage. On Jun 9, 3:29 am, Aaron <[email protected]> wrote: > Here is an example of the AppStats record for a sample page load. > This happens consistenly even when I"m only refreshing a static page. > As you can see, RPC's are extremely low, but Grand Total memory usage > is off the charts, which is requiring the application to cold start on > every load. > > http://grab.by/4POM > > On Jun 9, 12:21 am, Bill Edwards <[email protected]> wrote: > > > > > Hi GAE Team! > > > I am having a serious problem with my application. As of recently, > > every request that is being issued is resulting in the following > > error: > > > "After handling this request, the process that handled this request > > was found to be using too much memory and was terminated. This is > > likely to cause a new process to be used for the next request to your > > application. If you see this message frequently, you may have a memory > > leak in your application." > > > I believe as a result, every request is requiring a new instance to be > > loaded up in memory. This is giving me very high user latency. These > > problems did not prop up until the beginning of the datastore issues. > > > However, I have been talking to other GAE users, and they are not > > having the as serious problems as I am seeing. I would think that > > this may have something to do with my query usage. However, these > > errors prop up even on my static pages. > > > Please help me look for a solution to this problem. I greatly > > appreciate your time! -- 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.
