Re: Performance trouble at 35M rows
Posted by:
Ted Cui
Date: November 19, 2004 04:49AM
try InnoDB. It performs better on large tables comparing to MyISAM. Other place to looking into is to use larger disk extend block size.
You also can try larger sort buffer size which will be used when creating index.
After all, the size of the data matters. My theory is that the B-TREE index becomes inefficient when where are too many rows.
I have also noticed performance degression when table reached 40 Million range. But not as bad as you have described. So, try InnoDB first.
Meanwhile, I am looking for solutions to partition the table.
Subject
Views
Written By
Posted
4621
November 05, 2004 11:47PM
2459
November 07, 2004 09:02PM
2543
November 10, 2004 06:55PM
2528
November 26, 2004 11:57PM
Re: Performance trouble at 35M rows
2437
November 19, 2004 04:49AM
2473
November 26, 2004 01:43AM
2503
November 27, 2004 09:21AM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.