Hi,
Working on v4.1 (and from what I read, soon to upgrade to 4.1.18) and
I'm dealing with an MyISAM table expected to idle at around 400 million
records. Since it is the back-end to a high volume web site, we are
trying to optimize the performance of the indexes.
I read in the manual that LOAD INDEX INTO CACHE has a option which
excludes the pre-loading of the leaf nodes. What I can't figure out
from reading the documentation is how much of the BTREE will be made of
leaves and how much of the higher index nodes.
For the key, I am considering either using the prefix of the user name
ie. CREATE INDEX username_ndx on username(8)... or create an
additional INTEGER field which will store a CRC32 of username, and use
that field as an index.
For an 8 byte key and the 20M records mentioned above, the calculations
provided in the manual show me that the resulting index will be (worst
case) 3.2-10e bytes but I certainly don't have 32G of RAM to load it
into.
How is LOAD INDEX INTO CACHE going to keep index access from
disk-thrashing and do I need to manually tune key_buffer_size to take
advantage of it?
--
- michael dykman
- [EMAIL PROTECTED]
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
