Author - Vadim Tkachenko

Returning to InnoDB scalability

I’m again returning to InnoDB scalability and related bug #15815 as it hurts many users and customers using multi-cpu servers.
Short intro into problem:
On 4-CPU box 1 thread executes full-table scan select query for 8 sec,
but with 4 threads – each thread executes query for 240 sec.
It is very strange as threads use only SELECT […]

Read more

Stack trace for x86_64 boxes

We are going to release several patches which are not included in official MySQL releases.
First one is automatically stack trace for x86_64 systems. Currently MySQL resolves stack in crash only for x86 boxes.
You can download patch for 5.0.22 source tree here.
How to use: place stack64.diff into main source dir; execute patch -p1 < stack64.diff. One [...]

Read more

FreeBSD tests

I’m continuing my experiments with different OS and today I tested FreeBSD 6.0 on my box.
(more details about box and benchmark see here https://www.percona.com/blog/2006/06/13/quick-look-at-ubuntu-606/).
Initially I was very pessimistic about FreeBSD, as results were (in transactions/sec, more is better.
for comparison the results from Suse 10.0):

InnoDB

threads
FreeBSD 6
Suse 10.0
Suse/ FreeBSD ratio

1
436.97
536.91
1.23

4
322.08
816.27
2.53

16
519.94
639.05
1.23

64
crash
547.07

256

357.09

MyISAM

threads
FreeBSD 6
Suse 10.0
Suse/ FreeBSD ratio

1
335.56
429.89
1.28

4
165.16
863.23
5.23

16
322.66
537.67
1.67

64
crash
516.00

256

346.65

The crash with […]

Read more

MyISAM concurrent insert

Arjen posted a good note about MyISAM concurrent-insert features, though I should mention concurrent-insert can be cause of
scalablity and peformance problems on SMP boxes, especially on queries processing range-queries. The reason of problems is POSIX read-write locks, which are used to protect key_buffer from concurrent changes and called for each processed row. More info […]

Read more