June 18, 2013

Post: INSERT INTO ... SELECT Performance with Innodb tables.

Innodb tables perform non locking reads, meaning unless you use some modifiers such as LOCK IN SHARE MODE or FOR UPDATE, SELECT statements will not locklocking read (shared locks) for table2 table. It also applies to similar tables with where clause and joins. It is important for tables

Post: SELECT LOCK IN SHARE MODE and FOR UPDATE

locking mode which means they never lock any rows and just use old row versions if they were updated. All said above appliesFOR UPDATE to your select and reduce deadlocks if you’re updating selected rows. As query…; – A lot of shared locks on Innodb table but no updates. Supporting MySQL hints “…

Post: Choosing innodb_buffer_pool_size

Innodb Buffer Size you can use. Typically you would see restriction applyingtables and otherwise running complex queries. It is usually much better to simply check it. Start MySQL With 10GB Innodb buffer pool forfor your Innodb tables but there are other things you need OS cache for – MyISAM tables

Post: How fast is FLUSH TABLES WITH READ LOCK?

Query | 62 | Flushing tables | flush tables with read lock | | 6 | root | localhost | test | Field List | 35 | Waiting for table | | | 7 | root | localhost | test | Querylock. There is no reason to take a lock at all for backing up only InnoDB data. Completely lock

Post: Innodb locking and Foreign Keys

applies to PARENT table – if you will try to delete row in PARENT table lockup in CHILD table will be performed with row lock performed. Innodbfor performance) to messages table you will have significant number of user ids locked in the user table which can stall queries working with users table

Post: Innodb undo segment size and transaction isolation

for other reasons such as taking row level locks which will prevent other transactions for execution, this however only appliesfor that transaction to require state of any row in Innodb table at that point in time. If you use READ-COMMITTED mode Innodb

Post: Falcon Storage Engine Design Review

for some applications bad for others. There is large amount of applications out where which are optimized for Innodblocking concurrency which can give you problems if you have lock intensive workload so many update queries have to wait for row level locks

Post: Innodb performance gotcha w Larger queries.

Innodb level, so I tried running the test with MyISAM tables instead. The process completed in 12 seconds for… .plt 18071 3.1113 no-vmlinux no-vmlinux (no symbols) Which shows some …for each time. if (trx->isolation_level select_lock_type != LOCK_NONE && trx->mysql_query_str) { /* Scan the MySQL query

Post: Distributed Set Processing with Shard-Query

for all the queries to finish, then projects the synchronously maintained incrementally refreshable materialized view that represents the output. There is no external locking