Our database server has 4Gigs of ram on it, and we have a hard time of figuring out the true InnoDB settings on how to use that ram up. I ended up just increasing the ram used until it just wouldn't run anymore, then backed up and used that. We plan on adding another 4Gigs of ram, total of 8GB. Tweaking the InnoDB stuff doesn't seem as easy as the MyISAM side.
So as it stands, we have 4GB, and one table that easily exceeds that, almost 8GB in size. Even after we bump the server up to 8GB, that means this table will barely fit. Does that mean we need to start cleaning out that 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 > 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 the MySQL Administrator, and should be reported at http://bugs.mysql.com You can use SHOW TABLE STATUS LIKE 'table_name' to get the info about any given table. > > Also, does anyone know any of the magic numbers where things get difficult > for databases and tables and even the main server when it gets too big? There is no one magic number, but I define a couple of threshholds that could be of some guidance: * when the table does not fit into RAM anymore * when the most frequently accessed part of the table does not fit into RAM anymore However, the actual cut-off values for when the trouble starts is largely application dependent. -- Sasha Pachev AskSasha Linux Consulting http://www.asksasha.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
