Currently Mautic (Doctrine actually) uses the default mysql / mariadb transaction level which is REPEATABLE_READ
Drupal actually recommends to use READ_COMMITTED and as far as i can tell, this might also be beneficial for Mautic. Expecially in the case of table locks for high traffic tracking inside Mautic. However i did found some warnings to change this in a Doctrine application.
Moving to* READ_COMMITTED can improve concurrency and reduce deadlocks. However, with Doctrine, you must be more mindful that the entity data your PHP code holds might not reflect the latest committed database state throughout the entire transaction. Ensure your application logic, especially around optimistic locking and multi-step operations, is robust enough to handle this potential for data to change mid-transaction.
Hence my question, does anyone already tried this?