We're running sqlalchemy 0.7b4 (for internal reasons that aren't important here), but I've also tested this against 0.7.6(*). Both under Python3.2.2.
We have an application with about 60 tables in the (declarative) schema and perhaps 600 columns. After startup of the application, there are some 4000 event._ListenerCollection objects. While that class uses __slots__, it also allocates an empty list and an empty set in its __init__. I've managed to reduce our startup memory usage by 600K by hacking _ListenerCollection to not pre-allocate these empty objects. Is it normal for this many _ListenerCollections objects (and presumably a bunch of other Event related objects) to get pre-allocated, or are we doing something wrong in our configuration of the schema? --RDM (*) 0.7.6 uses about 2MB more memory at ap startup than 0.7b4 does. I haven't tried to investigate why; I just found this out when I ran my tests against it before sending this post. -- You received this message because you are subscribed to the Google Groups "sqlalchemy" 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/sqlalchemy?hl=en.
