I am always cautious of memory tables. They don't support transactions, for example, and don't work well multi user.
Really, the first stop is to use tokudb backend in mysql. If its still slow, and if you have a small subset that fits in ram, just put that straight into a hash table in app space.
Comments
I am always cautious of memory tables. They don't support transactions, for example, and don't work well multi user.
Really, the first stop is to use tokudb backend in mysql. If its still slow, and if you have a small subset that fits in ram, just put that straight into a hash table in app space.
As I understood it, the memory tables are read-only. They're like a cache. So transactions aren't needed.
Except for that awkward time when the tables are refreshed?
Could use two memory DBs and rotate them