This project is read-only.

Transaction isolation level default value

Topics: Customizing Orchard, General
Mar 27, 2013 at 11:30 PM
Edited Mar 27, 2013 at 11:31 PM
May be I have misunderstood but it seems that the Orchard new default transaction is set to READ COMMITED.

I would say that :
1) It would be better to let this decision 'SQL server side', and not forcing the sql server configuration because 'something' other than Orchard could access it.
2) if NHibernate doesn't allow letting this to the server settings value, we should preferably use as default READ UNCOMMITED because:
  • Orchard uses many small tables and small number of acces/table and one transaction will include access to several tables. So the COMMITED will lock all the tables until the end of the winning transaction, locking all the others
  • as far as the number of HTTP server requests increases the only solution is UNCOMMITED.
These results were deducted from a large prepaid telephony system (5M users) where sql server was managing the cards and the list cost routing with thousand connections/ second. Same pb as a web server.