Weblog entry #1 for cd
#1
MySQL on amd64
Posted by cd on Thu 9 Mar 2006 at 11:18
If you ever try to run a high load mysql on amd64 with Debian-Sarge: Forget it.
After many hard days, we found this:
http://bugs.mysql.com/bug.php?id=8555
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=314408
Switching to 32Bit mode works, but there is a loss of 10-20% performance :(
No we have a new problem - when we get close to 4000qps, we ran out of threads:
ERROR 1135 (00000): Can't create a new thread (errno 12); if you are not out of available memory, you can consult the manual for a possible OS-dependent bug
I now wait for a call from MySQL AB.
After many hard days, we found this:
http://bugs.mysql.com/bug.php?id=8555
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=314408
Switching to 32Bit mode works, but there is a loss of 10-20% performance :(
No we have a new problem - when we get close to 4000qps, we ran out of threads:
ERROR 1135 (00000): Can't create a new thread (errno 12); if you are not out of available memory, you can consult the manual for a possible OS-dependent bug
I now wait for a call from MySQL AB.
Comments on this Entry
The page you cite,
http://bugs.mysql.com/bug.php?id=7254
mentions that it's actually a libc6 bug, #314408
The changelog of libc6 claims this bug is fixed in version 2.3.5-3
http://packages.debian.org/changelogs/pool/main/g/glibc/glibc_2.3 .5-13/changelog#versionversion2.3.5-3
What libc6 are you using?
http://bugs.mysql.com/bug.php?id=7254
mentions that it's actually a libc6 bug, #314408
The changelog of libc6 claims this bug is fixed in version 2.3.5-3
http://packages.debian.org/changelogs/pool/main/g/glibc/glibc_2.3 .5-13/changelog#versionversion2.3.5-3
What libc6 are you using?
[ Parent | Reply to this comment ]