Hi, performed the test on 2.9.11-stable+timestamp.2014.09.15.23.35.11 (Running on Apache/2.4.7 (Ubuntu), Python 2.7.6):
I utilised apache benchmark (ab), making 1130 request within a minute twice with and without log.close(). I did not notice any memory leak, (neither with the log nor with the os memory check). When I performed the test manually within the browser without adding "log.close()" I noticed the increase in memory usage but that was before the garbage collector interfered and normal I guess (as the size of the text file increases the memory consumed by it increases). I did this test just to be relevant with this post but I must admit I would notice a memory leak as I run several sites with web2py and my servers would complain about it long before, surely, I am talking within my configuration. I use apache2 and mod_wsgi both in development (OS X) and production (Ubuntu). 4 Şubat 2015 Çarşamba 21:27:11 UTC+2 tarihinde Louis Amon yazdı: > > I have rather alarming news : > > Just to make sure, I've pulled the latest Git checkout of web2py and > created a new scaffolding app in which I put a memory usage logging > statement. > > Just by spamming refresh on my browser, the memory usage doubled over a > few hundred requests. > > > You'll find attached the log file that basically prints "URL memory_usage" > for each request + the application I used to make this test. > > > Can someone replicate this ? > Are memory leaks tested upon w2p releases ? > -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
