Are you sure you want to use MMAP in your database management system? [pdf]
1–10 of 137 posts
Re: Are you sure you want to use MMAP in your database management system? [pdf]
#2RavenDB's response to this paper: https://ayende.com/blog/196161-C/re-are-you-sure-you-want-to...
Re: Are you sure you want to use MMAP in your database management system? [pdf]
#3Url changed from https://db.cs.cmu.edu/mmap-cidr2022/, which has the abstract and a link to this video:
https://www.youtube.com/watch?v=1BRGU_AS25c
and this code: https://github.com/viktorleis/mmapbench
Re: Are you sure you want to use MMAP in your database management system? [pdf]
#4why settle for errno when you can have a segfault.
Re: Are you sure you want to use MMAP in your database management system? [pdf]
#5[deleted]
Re: Are you sure you want to use MMAP in your database management system? [pdf]
#6Do they mean: mmap() ?
Re: Are you sure you want to use MMAP in your database management system? [pdf]
#7[deleted]
Re: Are you sure you want to use MMAP in your database management system? [pdf]
#8RavenDB's response to this paper: https://ayende.com/blog/196161-C/re-are-you-sure-you-want-to...
The really key part seems to be this:
"If you aren’t using mmap, on the other hand, you still need to handle of all those issues"
Which seems like a reasonable statement. Is it less work to make your own top-to-bottom buffer pool, and would that necessarily avoid similar issues? Or is it less work to use mmap(), but address the issues?
Re: Are you sure you want to use MMAP in your database management system? [pdf]
#9Check out the creative use of emoji in the running header!
Re: Are you sure you want to use MMAP in your database management system? [pdf]
#10RavenDB's response to this paper: https://ayende.com/blog/196161-C/re-are-you-sure-you-want-to...
The really key part seems to be this: "If you aren’t using mmap, on the other hand, you still need to handle of all those issues" Which seems like a reasonable statement. Is it less work to make your own top-to-bottom buffer pool, and would that necessarily avoid similar issues? Or is it less work to use mmap(), but address the issues?
When I worked on/with BerkeleyDB in the late 90s we came to the conclusion that the various OS mmap() implementations had been tweaked/fixed to the point where they worked for the popular high profile applications (in those days: Oracle). So it can appear like everything is fine, but that probably means your code behaves the same way as .