On Nov 19, 2009, at 4:34 PM, bdb112 wrote: > > Any advice would be welcome. > > THe following should be read in monosapce font. > > Action Uptime Threads Questions Slowqurs Opens Flushtbls Opentbls > Qupersec dcpu > data1 35 2 1594 0 27 1 20 > 45.542 2.6 > repeat1 75 2 2161 0 27 1 20 > 28.813 7.7 > data02 134 2 4984 0 27 1 20 > 37.194 14.5 > data1 158 2 5545 0 27 1 20 > 35.94 17.7 > session.close() then > data1 96 2 7130 0 27 1 20 > 74.270 2.47 > speed is back to normal
this behavior is likely due to a known issue that was fixed in version 0.5.4. It involves a full scan of all objects in the current unit of work each time flush() runs, so the more objects present in your session, the slower each flush() operation becomes. There are lots of speed improvements to be had if you get on the latest 0.5 and in particular this one is the most dramatic - 0.5.4 also greatly improved the memory usage of the session such that unreferenced objects are garbage collected more readily. Within 0.4 your only option would be to keep the size of the session very small - this is possible but its a lot easier just to upgrade to 0.5.6. -- 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=.
