From: Sinisa Milivojevic <sinisa@mysql.com>
To: pz@spylog.ru
Cc: mysql@lists.mysql.com, linux-kernel@vger.kernel.org
Subject: Re: MYSQL,Linux & large threads number
Date: Fri, 15 Mar 2002 16:01:17 +0200 [thread overview]
Message-ID: <15505.65197.493625.894647@sinisa.nasamreza.org> (raw)
In-Reply-To: <551905871007.20020315163038@spylog.ru>
In-Reply-To: <551905871007.20020315163038@spylog.ru>
Peter Zaitsev writes:
> Hello mysql,
>
> Some time ago I wrote about slow down of mysql with large number of
> threads, which is quite common in Linux-Apache-Mysql-PHP enviroment.
>
> The test was simulating the worst case of concurrency - all the
> threads are modified global variable in a loop 5000000 times in
> total, using standard mutex for synchronization. The yeild is used
> in a loop to force even more fair distribution of lock usage by
> threads and increase context switches, therefore it did not change
> much with large number of threads. I.e with 64 threads time without
> yeild is 1:33.5
>
> Test was run on PIII-500 1G RAM Kernel 2.4.18. 3 runs were made for
> each number of threads and best results were taken:
>
> Num threads. Time Peak cs rate.
> 2 53.4 179518
> 4 53.8 144828
> 16 1:06.3 85172
> 64 1:48.1 48394
> 256 8:10.6 10235
> 1000 36:46.2 2602
>
I hope you are using latest glibc 2.2 with our patches applied.
Also please try adaptive mutex. How to set it, take a look at
mysys/my_thr_init.c.
--
Regards,
__ ___ ___ ____ __
/ |/ /_ __/ __/ __ \/ / Mr. Sinisa Milivojevic <sinisa@mysql.com>
/ /|_/ / // /\ \/ /_/ / /__ MySQL AB, Fulltime Developer
/_/ /_/\_, /___/\___\_\___/ Larnaca, Cyprus
<___/ www.mysql.com
next prev parent reply other threads:[~2002-03-15 14:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-15 13:30 Peter Zaitsev
2002-03-15 14:01 ` Sinisa Milivojevic [this message]
2002-03-18 19:35 ` Bill Davidsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=15505.65197.493625.894647@sinisa.nasamreza.org \
--to=sinisa@mysql.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mysql@lists.mysql.com \
--cc=pz@spylog.ru \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®