That's the thing. When I remove all functionality of my app and simply create
a new one whose only function is to return a json object of {test:memory} I
see this behavior. I was thinking that perhaps the memory was climbing because
I was importing a module at the wrong place or something.
Keep us posted. There is one thing that can cause a leak. Instantiating an
object with __del__ method at every request. It is possible that a third
party library does that if you import it and all one of its functions.
Another thing is cache ram. Another is T(something) where something is
I tried your example but I cannot reproduce the problem (I am on Mac, OSX
10.7.5 and Python 2.7.3).
Can others reproduce it?
On Tuesday, 5 February 2013 13:15:45 UTC-6, pumplerod wrote:
I'm reading up on strace now. in the meanwhile, here is the MVC code
(not sure if I can attach a file
Strange. In order to get around the issue I converted it over to run on GAE.
This seems to work ok. I notice thought that we're averaging about 2 requests
per second.
On Feb 10, 2013, at 3:35 PM, Massimo Di Pierro wrote:
I tried your example but I cannot reproduce the problem (I am on
2 requests/second seem slow. What does your app do? Look at
{{=response.toolbar()}} and see which DB query and how long they
individually take.
On Sunday, 10 February 2013 21:49:57 UTC-6, pumplerod wrote:
Strange. In order to get around the issue I converted it over to run on
GAE. This
I'm reading up on strace now. in the meanwhile, here is the MVC code (not
sure if I can attach a file to google groups)….
Model:
-Nothing. I have an empty model file. Other than the default settings that
come with a new controller.
Ordinarily I am using a Model and writing to the SQLite
I had been having critical memory overflow problems and finally saw a post
about a memory leak in the version I was using (2.1.x) so I have updated to
the latest stable version (2.3.2), however I am still seeing my memory
climb until the machine crashes.
I'm using web2py as my interface which
7 matches
Mail list logo