Re:RethinkDB internals: handling stack overflow on custom st...
by coffeemug on Friday December 31, 2010 @05:48AM
(#2055112)
Address space exhaustion is a problem, sure, but it has nothing to do with the buffer cache. The kernel's address space is completely separate from any particular process' address space.
For various reasons we don't use the kernel's cache, we have our own cache implementation that's in the same address space as the rest of the process.
Re:RethinkDB internals: handling stack overflow on custom st...
by cperciva on Friday December 31, 2010 @05:52AM
(#2055117)
Oh dear god.
You have my sincere and profound sympathies.
Re:RethinkDB internals: handling stack overflow on custom st...
by barrkel on Friday December 31, 2010 @05:55AM
(#2055122)
It's pretty unusual for databases to delegate something as vital to performance as caching to the OS.
Re:RethinkDB internals: handling stack overflow on custom st...
by cperciva on Friday December 31, 2010 @05:59AM
(#2055128)
Sure, a database needs to cache. But it doesn't automatically need to cache at that level -- usually they can get away with caching data rather than pages.
Re:RethinkDB internals: handling stack overflow on custom st...
by strlen on Wednesday January 05, 2011 @06:00PM
(#2072946)
If you have your own cache and you don't use direct I/O i.e., they go through the OS page cache, don't have you have the issue of the OS page cache and the database "fighting" each other?
Say again?
Address space exhaustion is a problem, sure, but it has nothing to do with the buffer cache. The kernel's address space is completely separate from any particular process' address space.