MySQL: index for a very large table

[solmyr72]

This is the first time I try to use MySQL for very large tables.
Up till now I used if for small tables, and was very pleased (great job, guys - thanks).

Experienced users warned me against possible problems with *index* definition for large tables:
they claim MySQL indices are stored completely in memory, which is problematic to me : I have a huge table and limited memory size (RAM). I did the math, and the entire index just won't fit into the RAM.
Unfortunatelly it will be a while before management approves hardware improvements.

Could anyone please advise whether MySQL really needs to store the entire index in memory ?
Or is there some way to configure this ?

Thanks very much !

 

[sleipnir214]

Are your experienced users able to provide references from which they gleaned the information that MySQL stores all indeces in memory? The section of the MySQL online manual titled "How MySQL uses memory" (link) does not include this.

Of course, since MySQL has a modular architecture, this could depend on the database engine being used.



Want the best answers? Ask the best questions! TANSTAAFL!

 

[KarveR]

Im sure Iposted on here that the memory allocation was a tunable server parameter, however, for anyone interested:
how musqld uses memory

and server tuning parameters
server tuning parameters - most notably key_buffer_size

______________________________________________________________________
There's no present like the time, they say. - Henry's Cat.