Re: Avoiding table-locking in big tables
> Anyway, performance is not the matter for us, we could add ram and cpu if we want.
Adding hardware is not a panacea.
Furthermore, the performance of the "report" seems to be the cause of the problem.
Switching from MyISAM to InnoDB may alleviate the Locks. MyISAM uses table locks; InnoDB uses row-level locking. Your description sounds like a table lock.
Please provide the SELECT that is used by the report -- perhaps we can make it faster.
If you are doing WHERE keyword LIKE '%...' (with a leading wild card), then such queries are doing a table scan. The table is 10GB; that will take a long time even with enough RAM to cache all of it, and a much longer time if you don't have enough.
How much RAM do you have?
Subject
Views
Written By
Posted
3832
April 19, 2011 10:40AM
1610
April 23, 2011 01:06PM
1714
May 14, 2011 01:23AM
Re: Avoiding table-locking in big tables
1878
May 14, 2011 01:16PM
1615
May 15, 2011 02:19PM
1694
May 15, 2011 11:46PM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.