Hi,
randyboy:
> Thanks for all the responses. However, I'm still wondering, in the heap
> method and in the stick-bit copy all into memory method, how does one
> maintain synchronicity between the db on disk and the copy in memory?
>
The sticky-bit method (which should really be a no-op (*)) simply says to
keep the file cached. It's still basiclly stored on disk.
With a HEAP table, you have to do the syncing yourself (load it from
another table when the server starts, dump it to disk every quarter hour or
whatever).
*) The semantics of sticky bits I'm familiar mit just control whether the
file stays in memory when nobody has it open, which should never happen
with MySQL because it LRU-caches open files.
Some OSes, like Linux, just ignore the bit, as there is no reason at all
not to keep the thing in memory (if some is free) anyway. "If some is
free" translates to "give the thing enough so that it's not swapping
(much)", which is a very good idea anyway. ;-)
--
Matthias Urlichs | noris network GmbH | smurf@stripped | ICQ: 20193661
The quote was selected randomly. Really. | http://www.noris.de/~smurf/
--
Women have more strength in their looks than we have in our laws, and
more power by their tears than we have by our arguments.
-- Saville
