Re: Subtly Bad Things Linux May Be Doing To PostgreSQL
by twoodfin on Thursday April 03, 2014 @04:57PM
(#7526589)
Interesting. When I read your first comment, I didn't realize you meant "bypass kernel" in as wide a scope as you describe here. Usurping CPU scheduling, in particular, was something I didn't think was common practice. Can you name a (presumably commercial) DBMS that represents this kind of "self-manage everything" architecture?
Re: Subtly Bad Things Linux May Be Doing To PostgreSQL
by jandrewrogers on Thursday April 03, 2014 @10:54PM
(#7528902)
Most of the big "enterprise" OLTP databases are designed this way; the less portable they are, the more likely they are doing deep bypass optimizations. DB2, SQL Server, and similar are bypass designs. Oracle used to be a weird hybrid, due to portability requirements, but since they took control of the hardware I would assume recent versions are mostly pure bypass.
Most commercial analytical databases are not bypass, due in large part to the fact that most of them are based on Postgres, ironically.
Once you have these resources, you can organize them and use them as you see fit. Because it is not going to the kernel for any resources or buffering or scheduling or memory etc, there is little opportunity for the OS to do the wrong thing with resources that already are tightly controlled by the runtime. However, this is also why it is an "all or nothing" kind of situation.