Timeline for Should we need to use Barriers on a production database (MySQL/InnoDB)?
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 25, 2018 at 6:26 | comment | added | Sybil |
can I disable that on Vmware barrier=0 and ext4 filesystem? For performance reasons?
|
|
| S Jul 13, 2012 at 16:50 | history | suggested | Mat | CC BY-SA 3.0 |
Minor typo/english fixups
|
| Jul 13, 2012 at 16:42 | review | Suggested edits | |||
| S Jul 13, 2012 at 16:50 | |||||
| Jul 13, 2012 at 16:08 | comment | added | Yoga |
It seems to me not many are using barrier=1 in production server, right?
|
|
| Jul 11, 2012 at 8:41 | comment | added | ypercubeᵀᴹ | And the 2 years old post by Mark Callaghan, describing the issue and the Facebook patch. | |
| Jul 11, 2012 at 8:30 | comment | added | ypercubeᵀᴹ | And the blog of Kristian Nielsen, who has worked on these optimizations: kristiannielsen.livejournal.com | |
| Jul 11, 2012 at 8:28 | comment | added | ypercubeᵀᴹ | Also this benchmark which compares Facebook's patch and MariaDB's: Group commit in MariaDB is fast. Rumors say that MySQL 5.6 will include a similar optimization: Binary Log Group Commit in MySQL 5.6 | |
| Jul 11, 2012 at 8:23 | comment | added | ypercubeᵀᴹ | And lately, several versions of MySQL have some optimizations on how they are doing fsyncs, to improve performance. See: MariaDB: Group commit for the binary log | |
| Jul 11, 2012 at 8:16 | history | answered | Eelke | CC BY-SA 3.0 |