[EMAIL PROTECTED] wrote:
Unlikely, unless you have more writes than reads, which would be rather unusual for most applications. :)
An index on a field with a selectivity of more than 15% can perform worse than a full table scan in most cases. That affects read performance as well as disk I/O and locks the table/rows for write access. Also, there is an index on mailbox_idnr plus one on mailbox_idnr AND status (in that order), which doesn't make sense, if the index is not a hash but a btree. That is btw the only index type for InnoDB. So the case is clear.
Anyway, the original poster said there is only one server being used, so all this replication/clustering is irrelevant in this particular case.
A cluster always is the last thing that helps. I did not recommend that. But a cache is for sure not the worst idea one could come up with ;)
Michael _______________________________________________ DBmail mailing list [email protected] https://mailman.fastxs.nl/mailman/listinfo/dbmail
