Ivan Sagalaev wrote: > When it comes to overhead... As far as I know PostgreSQL in autocommit > mode will wrap each statement (even SELECT) in an implicit transaction. > > http://it.toolbox.com/blogs/database-soup/postgresql-application-performance-tips-part-1-13172 ... > So what Django does now ... is actually more efficient then equivalent in > auto-commit mode
That's an interesting article, and I follow your logic. However, Jack's original patch follows from profiling work he did on his Chesspark site (see http://metajack.wordpress.com/2007/07/25/do-you-know-what-your-database-is-doing/ ) in which he claimed a 2-3x speed improvement from changing to auto- commit mode. I haven't done the equivalent testing myself, and would be interested in an explanation of why your article and his tests give such different conclusions. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" 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/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
