Re:RethinkDB internals: handling stack overflow on custom st...
by coffeemug on Friday December 31, 2010 @05:52AM
(#2055118)
I am not sure why they are writing their own library
We aren't, our code is based on a slightly modified version of libcoroutine. We've just added a few bells and whistles here and there to do a little bit more than what the library offers out of the box.
I don't think they are doing a ton of socket IO, so perhaps that is where their need to reinvent comes from.
Our real-world load can easily change between between disk bound, network bound, and CPU bound, so we need to support both IO bound and CPU bound workloads really well.
We aren't, our code is based on a slightly modified version of libcoroutine. We've just added a few bells and whistles here and there to do a little bit more than what the library offers out of the box.
I don't think they are doing a ton of socket IO, so perhaps that is where their need to reinvent comes from.
Our real-world load can easily change between between disk bound, network bound, and CPU bound, so we need to support both IO bound and CPU bound workloads really well.