From a purist point of view, it would be wrong to use a transaction in SELECT statements to improve performance. Use a transaction to avoid data inconsistencies.
In terms of performance, locking tables so that no other operator can access it to speed up SELECT but perhaps there are better solutions than this. For example, use the attribute attribute SELECT statement : HIGH_PRIORITY
HIGH_PRIORITY gives SELECT higher priority than the statement that updates the table. You should use this only for very quick requests and should be done right away. CHOOSE A HIGH HOLIDAY query that is issued while the table is locked for reading, even if there is a pending update so that the table is free. This affects only storage that use table-level locking (for example, MyISAM, MEMORY, and MERGE).
, - , ( ) , .