Jonathan Chong wrote:
I have a table on my forum that's frequently accessing with reads and
writes. On a busy day, the table is locked when people are posting
messages and the page hangs when you try to read a topic.
Is it worth me converting the table to InnoDB, as I've heard that
InnoDB doesn't lock tables during I/O access.
InnoDB has row-level locking (i.e. it basically only locks the rows that
might be changed by the query). InnoDB is generally speaking a good
choice in 'high concurrency' situations (many reads and writes at the
same time); for small read-only or write-only tables InnoDB is usually
slower than MyISAM.
In your situation it might solve the locking problem. Do read the online
manual carefully since there are a lot of differences between MyISAM and
InnoDB (the way data is stored, the way indexes are stored, some
differences in handling statements and functions,etc.)
Regards, Jigal.
smime.p7s
Description: S/MIME Cryptographic Signature
