InnoDB Testing, Discussion Results

Benton, Kevin kevin.benton at
Tue Aug 8 20:16:28 UTC 2006

> On 08/08/06, Max Kanat-Alexander <mkanat at> wrote:
> >         Looking into it (using MySQL's slow query log), I did find
> under
> > high numbers of simultaneous users, certain buglist searches do
spend a
> > lot of time waiting for WRITE locks on the database to release. That
> > every time somebody uses process_bug or post_bug, it's going to slow
> > down queries. If we were under transactions, this would end.
> We shouldn't have WRITE locks for any period of time. If you're not
> doing replication, what you'll find is that readers block writers - ie
> you're waiting for WRITE locks, because someone else has a read log.
> You may want to test that - it will improve, but you'll still have row
> level exclusive locks (yes, its more complicated than that, but for
> our purposes...)

If we do this, we have to be especially careful to make sure we release
locks explicitly using mod_perl.

Kevin Benton
Perl/Bugzilla Developer/Administrator, Perforce SCM Administrator
AMD - ECSD Software Validation and Tools
The opinions stated in this communication do not necessarily reflect the
view of Advanced Micro Devices and have not been reviewed by management.
This communication may contain sensitive and/or confidential and/or
proprietary information.  Distribution of such information is strictly
prohibited without prior consent of Advanced Micro Devices.  This
communication is for the intended recipient(s) only.  If you have
received this communication in error, please notify the sender, then
destroy any remaining copies of this communication.

More information about the developers mailing list