And yet again the problem is not in SQLAlchemy but in Pyramid.... Sorry,
from now on, I'll first try writing test scripts without Pyramid to see
where the problem is, I just don't have time for that kind of debugging
so I'm wasting yours. :)
Thanks. I'll write to Pylons Discuss list, but the test script is here
nevertheless. Comment out line 266 (and remove imports) to disable
Pyramid and see it work okay. Without Pyramid (but even with Transaction
and ZopeTransactionExtension), the gcdelta is 0 or negative per batch of
200 iterations. With Pyramid bootstrapped, gcdelta is in thousands per
batch of 200 iterations.
https://gist.github.com/d669e958c54869c69831
.oO V Oo.
On 02/23/2012 02:41 AM, Michael Bayer wrote:
On Feb 22, 2012, at 6:36 PM, Vlad K. wrote:
Okay, thanks to this article:
http://neverfear.org/blog/view/155/Investigating_memory_leaks_in_Python
I made similar plot of object counts in time, showing top 50 types. The
resulting PDF is here (you might wish to download it first, Google messes it up
for me):
https://docs.google.com/open?id=0ByLiBlA59qDwYTY1MGIzYWEtYjMxZi00ZDVlLTk0OTEtOGI2ZjA3NDgyM2Y3
Everything seems to linearly grow in count. Something is keeping all those
objects reference somewhere. What could possibly be the cause?
can you provide a self-contained, single file test case that illustrates the
memory growth ?
--
You received this message because you are subscribed to the Google Groups
"sqlalchemy" group.
To post to this group, send email to sqlalchemy@googlegroups.com.
To unsubscribe from this group, send email to
sqlalchemy+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/sqlalchemy?hl=en.
