MySQL optimization prior to Alfresco 3.4
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-20-2012 04:18 AM
Hi,
We have been advised to set innodb_locks_unsafe_for_binlog=1 in the MySQL configuration since Alfresco left Hibernate for iBatis in the DAO layer (see http://docs.alfresco.com/4.0/index.jsp?topic=%2Fcom.alfresco.enterprise.doc%2Fconcepts%2Fmysql-confi...). It prevents MySQL from locking too many rows when accessing tables, and thus eases concurrent accesses, but can cause inconsistent reads.
Did someone experienced this configuration in older Alfresco versions, like 3.2 or 3.3, with MySQL 5.1?
We have been advised to set innodb_locks_unsafe_for_binlog=1 in the MySQL configuration since Alfresco left Hibernate for iBatis in the DAO layer (see http://docs.alfresco.com/4.0/index.jsp?topic=%2Fcom.alfresco.enterprise.doc%2Fconcepts%2Fmysql-confi...). It prevents MySQL from locking too many rows when accessing tables, and thus eases concurrent accesses, but can cause inconsistent reads.
Did someone experienced this configuration in older Alfresco versions, like 3.2 or 3.3, with MySQL 5.1?
Labels:
- Labels:
-
Archive
1 REPLY 1
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-03-2013 11:24 AM
Any idea?
