If a table is frequently written from front end and same table has to be as frequently searched as well. Both are performance critical.
For example a POST table whic
This depends on the Storage Engine of the Table
InnoDB supports MVCC and 4 Transaction Isolation Levels
This allows for INSERTs, UPDATEs, DELETEs, and SELECTs to live harmoniously 99.999% of time
This is a totally different playing field. By default, every INSERT, UPDATE, and DELETE locks the entire table. INSERTs can have table locking disabled by setting concurrent_insert to 2. (See Concurrent Inserts for more information). Otherwise, UPDATEs and DELETEs can still wreak some havoc doing full table locks.