I'm not thinking of hot cell caching. I'm talking about going the
whole way and putting all the data in-memory. So yes, store file
contents would be loaded into memory, though not the memcache,
because that would get really complicated, I think. InMemoryStoreFile
would really be what I was going for, I'd guess. The table wouldn't
be read-only. Writes would go through to disk but reads would come
straight from memory.
On Mar 31, 2008, at 8:42 PM, stack wrote:
A Reference-cache of hot cells would take a day at the outside I'd
guess. The bulk of the work is done.
If you're talking about something else, lets discuss. What would
it look like? Store MapFiles would be floated in memory or copied
to MemCache? We'd need a special In-Memory MapFile? We'd do a
bulk memcopy from HDFS up into mem and then you'd serve from
there? Would the table have to be read-only?
St.Ack
Bryan Duxbury wrote:
Quick poll for us devs - if you had to guess, how long do you
think it would take for the in-memory option of HBase to actually
be implemented to work reliably?
-Bryan
