Once your tables' engine are all of innodb, your configuration file has to
be changed to fit innodb's feature, not myisam.
On Tue, Apr 21, 2009 at 2:09 PM, living liquid | Christian Meisinger <
c.meisin...@livingliquid.com> wrote:
> ah sorry... there are a few UPDATEs too but most is SELECTs...
ah sorry... there are a few UPDATEs too but most is SELECTs...
60:40 i would say.
> Excuse me. But why concurrent queries request table locks?
>
> 2009/4/20 living liquid | Christian Meisinger
>
>> Hi there.
>>
>> I've a small table with my daily banner hits.
>> 1. version was with myisam but
MyISAM should be fine with many SELECTs running at once. Tables are
only locked for INSERTs DELETEs and UPDATEs, and conditionally at
that. You can set MySQL to always append INSERTs to the end of the
file so you can insert while selecting.
What is the whole picture? If you were having locking pro
change connect timeout to 10sec
flatly use skip-name-resolve
whats the total size of your database.
On Mon, Apr 20, 2009 at 7:58 PM, living liquid | Christian Meisinger <
c.meisin...@livingliquid.com> wrote:
> Hi there.
>
> I've a small table with my daily banner hits.
> 1. version was with myis
Hi there.
I've a small table with my daily banner hits.
1. version was with myisam but with a lot of concurrent queries (all SELECTs) i
get too many table locks.
so i changed it to an innodb table.
works great most of the time.
sometimes it seems to be too much, starting at about 500 concurrent
