Configure MySQL transaction isolation level to READ UNCOMMITTED in tracking to avoid gap locks. READ COMMITTED for better performance overall #14619
Labels
c: Performance
For when we could improve the performance / speed of Matomo.
not-in-changelog
For issues or pull requests that should not be included in our release changelog on matomo.org.
Task
Indicates an issue is neither a feature nor a bug and it's purely a "technical" change.
Milestone
Goal: minimise possible locks in Tracker to improve performance.
Concerns: what could be the worst side effects? inconsistent tracking data stored in some cases?
Note: this should ONLY apply in Tracker mode, not for API/UI/etc.
https://dev.mysql.com/doc/refman/8.0/en/innodb-transaction-isolation-levels.html#isolevel_read-uncommitted
dirty read
The text was updated successfully, but these errors were encountered: