The problem isn't really if the database fits into RAM, it's if your
index does, if your searches use the index. Databases can easily
outgrow even the maximum RAM you could install on even a high end
machine. So while it's ideal to fit your database in RAM, it's not
always feasible. Your first
[snip]
...big...
[/snip]
We are running OpenBSD servers utilizing a dual Xeon processor
architecture with a 1TB RAID. We have a database using MyISAM
tables...here are some stats from phpMyAdmin on one database on this
server --
20 table(s) Sum 347,092,085 --149.6 GB
Two tablea in this
The maximum single file size of a system is as follows,
*Operating System* *File-size Limit*
Linux 2.2-Intel 32-bit 2GB (LFS: 4GB)
Linux 2.4 (using ext3 filesystem) 4TB
Solaris 9/1016TB
NetWare w/NSS filesystem8TB
win32 w/ FAT/FAT32 2GB/4GB
win32 w/ NTFS 2TB (possibly
Misao schrieb:
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?
We have a few 20-30GB-InnoDB-Tables (growing) without any problems
(mysql 4.1.5gamma).
The limits of mysql are somewhere in the t
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
>
Does anyone know the point that the MySQL Administrator can't report on
table sizes?
Misao:
I do not use MySQL Adminstrator, so I do not know at what point it is unable to
correctly report the size of a table. But if there exists a table that it cannot
correctly report the size of, it is a bug in
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
