Our production databases here are really growing and getting to be rather
big. The question on our minds is; when is a database or table just too big?
Our InnoDB datafile was 116GB last I checked, and I know we've got a few
20GB+ databases on there, but my real concern is over the table sizes. I
ha
table, or
adding new ram?
-Original Message-
From: Sasha Pachev [mailto:[EMAIL PROTECTED]
Sent: Thursday, January 27, 2005 6:52 PM
To: Misao
Cc: mysql@lists.mysql.com
Subject: Re: How big is too big?
>
> Does anyone know the point that the MySQL Administrator can't report on
>
I'd have to say that things look fine in that regard.
core file size (blocks) 0
data seg size (kbytes) unlimited
file size (blocks) unlimited
max locked memory (kbytes) unlimited
max memory size (kbytes)unlimited
open files 1024
pipe size (512 bytes) 8
First off to maybe make this easy on you, you do not need the
MySQL-bench rpm if you do not plan on using the benchmarking tools. It
is an optional install.
Otherwise, I do not think rpm cares about capitalization. I believe this
problem is discussed in the MySQL manual, and might have the solut
What follows is a short story, all true and quite stressful. No database
servers were harmed in the making of this server, but a couple were
threatened with loose rack mount rails.
We are trying to move over to InnoDB, but we have a few problems that we
just can't figure out:
First, for some r
I have 4 MySQL 4.0.16 servers, all with Dual 3ghz Xeons and 4GB of RAM.
They use InnoDB for all tables, and the ibdata file is 70GB.
The DBs seem to be a little slow, and the darn thing is always using a huge
chunk of swap. I've tried increasing and decreasing what it's allowed to
use, but this see
]
Sent: Friday, June 11, 2004 7:45 AM
To: [EMAIL PROTECTED]
Subject: Re: Server optimization issue
"Misao" <[EMAIL PROTECTED]> wrote:
Take a deep look at
http://dev.mysql.com/doc/mysql/en/Server_system_variables.html
But ensure that this is MySQL who takes so much memory. Watch othe
