How about the innodb_spin_wait_delay? I recommend it with smaller value of 30, even 0. In this way, ut_delay would not on the top of PerfTop.
Post: Scaling problems still exist in MySQL 5.5 and Percona Server 5.5
… btr_search_guess_on_hash 716506 12.4800 mysqld mutex_spin_wait 467974 8.1511 mysqld rec_get_offsets_func 376898 6…,start_thread,clone 4 pthread_cond_wait,os_cond_wait,os_event_wait_low,sync_array_wait_event,mutex_spin_wait,mutex_enter_func,pfs_mute… index makes things a lot worse in this workload and innodb_adaptive_hash_index_partitions=16 available for partitioning adaptive hash…
Post: How Innodb Contention may manifest itself
… wait is indeed more efficient than doing context switches, however sometimes there is just too much spinning and it becomes inefficient. Reducing innodb… time with context switching because Innodb is not spinning too much, thus you can consider increasing innodb_sync_spin_loops to a higher number…
Comment: SHOW INNODB STATUS walk through
… ———- OS WAIT ARRAY INFO: reservation count 50573942, signal count 48103669 Mutex spin waits 0, rounds 1286836814, OS waits 29544296 RW-shared spins 17771305, OS waits 8349871; RW-excl spins 10508828, OS waits 5276204 Currently I have innodb_sync_spin…
Comment: SHOW INNODB STATUS walk through
“…innodb_sync_spin_loops can be used to ballance between wasting CPU time running spin locks and doing unneeded context switches…” So if we have a very large amount of spin waits and spin rounds, will we increase innodb_sync_spin_loops or decrease it in order to reduce spin waits/rounds?
Comment: SHOW INNODB STATUS walk through
…innodb_sync_spin_loops can be used to ballance between wasting CPU time running spin locks and doing unneeded context switches….” So if I see very large amount of spin waits and spin rounds, will I increase or decrease the innodb_sync_spin_loops in order to reduce…
Comment: Returning to InnoDB scalability
… Count | Spin_waits | Spin_rounds | OS_waits | OS_yields | OS_waits_time | …| 53893011 | 940 | 3139 | 7 | 15 | 0 | | &srv_innodb_monitor_mutex | srv0srv.c | 21679 | 8 | 80 |…
Comment: Returning to InnoDB scalability
… Module | Count | Spin_waits | Spin_rounds | OS_waits | OS_yields | OS_waits_time | +—————————+————-+————–+————+————-+———-+———–+—————+ | …c | 1 | 0 | 0 | 0 | 0 | 0 | | &srv_innodb_monitor_mutex | srv0srv.c | 57877 | 0 | 0 | 0 |…
Post: New SpecJAppServer results at MySQL and Sun.
… innodb_log_buffer_size = 16M innodb_flush_log_at_trx_commit = 1 innodb_lock_wait_timeout = 300 innodb_thread_concurrency = 0 innodb_sync_spin_loops = 40 innodb_locks_unsafe_for_binlog = 1 innodb_max_dirty_pages_pct=15 innodb_support…
Post: MySQL 5.0, 5.1 and Innodb Plugin CPU Efficiency
… execution path. Another thing to note – if you’re using Innodb Plugin consider using new Barracuda format, though do this only… testing as this format will not be recognized by older Innodb versions. Note: These are completely CPU bound test conditions, data… threads to cause full CPU usage, or you may be waiting by spinning on the spinlock wasting CPU cycles. Detailed profiling tells…

