On Thursday 13 November 2003 10:19 am, Oliver Zeigermann wrote:As I recently discussed with Christophe some sort of write-back cache could not only buffer reading, but also writing. As described above it would be synced with persistent store upon commit (or upon prepare? hmmm, have to think about it... Comments?) or when it spills.
Unfortunately, this will make things really complicated as - AFAIK - the cache itself would need non-blocking locks and a complex spill protocoll. Not sure if it is worth it...after the experience with the DB store "optimization"... ;)
Wouldn't this mean that the entire store was cached? I would think this would be a problem for large sites.
No. You can configure the size of the cache. That's why I was talking about spilling. If the cache gets too big, some data must be written to persistent store. The combination of this, invalidation in the cache and locking seems to be tough to me.
Oliver
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
