Thread: mysql 4.1 - 50 Millieion records each year

I have came across a situation where app generates around 50 M records each year.. We are using mysql 4.1 and its not possible to upgrade at this time.. Can any one provide inputs, ideas on how this situation can be handled.. As far as I know 4.1 does not support partitioning... The table structure is very simple with few columns.. The problem is how to handle this many records in one table and still have decent performance.. Table structure...

There are many factors leading to performance, or lack thereof. Number of rows is rarely the primary cause of poor performance. Sorry, I need more than a sketch of the tables; please provide * SHOW CREATE TABLE tbl\G -- engine, indexes * SHOW TABLE STATUS LIKE 'tbl'\G -- sizes * EXPLAIN SELECT ...\G -- clues of inefficiencies * SHOW VARIABLES LIKE '%buffer%'; -- cache size and surround them with [ code ] and [ / code ] 50M...