You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 6, 2024. It is now read-only.
One of the main insights of the German's paper is that modern software is unable to exploit the full parallelism of modern hardware, specifically NVMe SSDs that use several PCIe lanes to get crazy throughput.
Right now, the buffer pool manager only supports 1 disk and 1 file. The DiskManager should be an interface that completely abstracts away the number of SSDs the hardware actually has. This also means that the DiskManager should be the one to set up an io_uring instance per disk per thread. For example, if there are 10 SSDs and N worker threads, the DiskManager needs to manage 10 io_uring instances per thread, which means 10 * Nio_uring instances.
I don't really know what this means for implementation, or if this is even possible. However, it seems like the Germans were able to get it to work, so theoretically we should be able to as well.
The text was updated successfully, but these errors were encountered:
One of the main insights of the German's paper is that modern software is unable to exploit the full parallelism of modern hardware, specifically NVMe SSDs that use several PCIe lanes to get crazy throughput.
Right now, the buffer pool manager only supports 1 disk and 1 file. The
DiskManager
should be an interface that completely abstracts away the number of SSDs the hardware actually has. This also means that theDiskManager
should be the one to set up anio_uring
instance per disk per thread. For example, if there are 10 SSDs andN
worker threads, theDiskManager
needs to manage 10io_uring
instances per thread, which means10 * N
io_uring
instances.I don't really know what this means for implementation, or if this is even possible. However, it seems like the Germans were able to get it to work, so theoretically we should be able to as well.
The text was updated successfully, but these errors were encountered: