for DB performance reasons we should change the current behaviour of SQL requests and boost drupal performance in this way. if we do only read-uncommitted requests we will not have deadlocks and i think drupal.org becomes more speedy then the sleeping speed today. i know implementing read-uncommitted will solve nearly all DB performance issues on big sites with traffic. We have a starting discussion about the how and why in http://drupal.org/node/74308#comment-212904 with MsSQL, but MySQL and others have the same feature and the way how this feature can be accomplish is the same...

Are you able to implement this for 6.0?

Comments

m3avrck’s picture

m3avrck commented

subscribing...

david strauss’s picture

david strauss
he/him
commented
Status: Active » Closed (won't fix)

Read-uncommitted is a bad idea. It allows inconsistent views of intratransaction states. Preserving atomicity is one of the primary functions of transactions. It's also hardly a performance cure-all. When this bug was posted, Drupal.org used MyISAM, which doesn't even have transactions. Even with InnoDB, Drupal core uses no transactions, so changing the transaction mode won't help.