My nightly processing failed on the latest version and it appears that the new
repr() functionality is causing some significant memory/processing overhead on
large data sets. I know I'm pushing things a little(!!! - its a darn good stress
test) but in one routine I'm loading all the records in a table (>189,000) and
SQLAlchemy is choking at this point, maxing out the memory (1GB) before getting
all the way through mapping these records. This has worked up until now (taking
only around 3min on my laptop) so I rolled back to the pre-repr() changes
(v800), added in the Postgres version code from 806 (apologies for the tabs btw)
and everything is working again. The repr() code is being called a lot, as it
looks to be used in generating the identity key, so it is obviously a
performance sensitive area. Can we retain the repr() benefits w/o adversely
affecting SQLAlchemy's performance?
Robert
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Sqlalchemy-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sqlalchemy-users
