Tadeu Alves wrote:
Thanks for this heads up i was thinking into some of these i was
looking into the page that has the calculation of each looking into
mysqlperformance blog
it's a good idea of add more memory into this variables?
query_cache_size= 1000M to 2000M and
innodb_buffer_pool_siz
Hi,
probably your system is swapping on disk,
immediately reduce the sort_buffer_size, it is a per connection buffer, and
your setting is way too high:
sort_buffer_size=1000M (with 8 client threads you finish your ram)
set it to something between 256K and 8 M
sort_buffer_size=1M
also
read_rn
Helo there guys today ive got a brig problem my server that runs only Mysql
is undegoind a very load, the server is ok but memory and cpu usage are very
high
mys server configuration is a
2x Quad Core Intel® Xeon® E5450, 2x6MB Cache, 3.0GHz, 1333MHz FSB
8GB 800MHz Memory
2x SAS 73GB 15000RPM in RA
Hi,
I have the following problem:
mysql Ver 14.12 Distrib 5.0.51a, for portbld-freebsd6.3 (i386) using 5.0
080605 15:33:26 - mysqld got signal 10;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly bui
Hi,
I have the following problem:
080605 15:33:26 - mysqld got signal 10;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardwa
At 09:45 AM 12/10/2007, thomas Armstrong wrote:
Hi
Using MySQL 4.1.19 on Linux, my server's CPU load is very high. I want
to cut it down but I don't know which parameters I might modify to do
it.
Post the "Show Full Processlist" and maybe we can figure out what MySQL is
doing to cause such a
Hi
Using MySQL 4.1.19 on Linux, my server's CPU load is very high. I want
to cut it down but I don't know which parameters I might modify to do
it.
These are my server's data:
back log50
basedir /usr/
bdb cache size 8,388,600
bdb home/var/lib/mysql/
bdb log buffe
Hey all, i'm trying to setup a system in which a slave takes over as master in the
case the master dies.
we're using innodb w/ databases of about 500 megs, so scp/rsyncing those every night
is a pretty daunting task, not to mention we can never be sure that the secondary DB
has the most recent
