Hi,
table_cache is 8 on our systems. I quick glance at the manual tells me to
increase that value (Opened_tables is 2680462406)... I will try that.
Thanks ;)
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 12, 2006 12:32 PM
To: Moritz Möller
cking issue, will grab the output of INNODB
STATUS the next time it happens.
Moritz
-Original Message-
From: Gabriel PREDA [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 12, 2006 11:22 AM
To: Moritz Möller
Subject: Re: mysterious speedup after doing "FLUSH TABLES"
See http://
Hi,
that variable is not set, so it should be the default value (2 * number of
processors I believe).
To what value should I set it?
-Original Message-
From: Gabriel PREDA [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 12, 2006 10:02 AM
To: Moritz Möller
Subject: Re: mysterious
Hello list,
we use MySQL 4.1.13 / InnoDB on Xeon em64t running Debian, kernel 2.6.8.
After a while, queries run slower and slower, although the CPU is >70% idle
and diskio is nearly zero. A simple select by primary key takes up to one
second. After doing a FLUSH TABLES the speed is up again.
I a
Hi,
i've noticed similar behaviour as we upgraded to mysql 5.0.
The query optimizer seems to been "optimized" a little too much :-\
-Original Message-
From: Szymon Kosok [mailto:[EMAIL PROTECTED]
Sent: Saturday, May 27, 2006 5:42 PM
Cc: mysql@lists.mysql.com
Subject: Re: MySQL 5 prob
; n), but still, every 2-3 days
the slaves got completely out of sync ("duplicate key" and other) :(
Moritz
-Original Message-
From: Jay Pipes [mailto:[EMAIL PROTECTED]
Sent: Thursday, May 25, 2006 6:37 PM
To: Moritz Möller
Cc: 'Dan Trainor'; mysql@lists.mysql
on application level (use
server userID%numServers), which would be a [insert favourite non-swear-word
here] lot of work ;)
Moritz
-Original Message-
From: Dan Trainor [mailto:[EMAIL PROTECTED]
Sent: Thursday, May 25, 2006 1:41 AM
To: Moritz Möller; mysql@lists.mysql.com
Subject: Re: my
Hi list,
we're running some large high-traffic mysql servers, and are currently
reaching the limit of our machines.
We're using mysql 4.1 / innodb on debian, ibdata is about 35GB. Hardware is
quad xeon dualcore, 8 GB RAM. Disk-io is nearly zero, limiting factor is
CPU.
The queries run very fast (
