That said, you will most likely hit the limits of your database design before you hit the limit of MySQL. If your database data doesn't change much, just gets added to, you should look at dimensional database design as opposed to traditional relational design. This starts getting you into the realm of datawarehousing, which has different design rules.
Two books that may be helpful are: High Performance MySQL from O'Reillly Designing Effective Database Systems from Addison Wesley
The first book would be helpful for scaling MySQL, the second will be helpful for creating a scalable design.
On Jan 27, 2005, at 7:08 PM, Misao wrote:
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?
-- Brent Baisley Systems Architect Landover Associates, Inc. Search & Advisory Services for Advanced Technology Environments p: 212.759.6400/800.759.0577
-- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
