Remix.run Logo
dboreham 3 days ago

Almost full-circle back to when Oracle took over the entire volume and implemented its own filesystem.

dale_glass 3 days ago | parent [-]

I wonder why this is not more common. LVM is easy to set up, and it's already common to allocate volumes for things like disk images for VMs, so why not databases?

jandrewrogers 3 days ago | parent | next [-]

Some Linux filesystems, notably ext4 and XFS, provide the necessary features to get 90% of the benefit simply by using O_DIRECT correctly. The last 10% is achieved by doing direct I/O to raw block devices, with the obvious caveat that this is not as easy to manage.

Both of these are commonly done in database storage engines.

tptacek 3 days ago | parent | prev | next [-]

If you preallocate and O_DIRECT, haven't you basically soaked up most of the benefit of skipping the filesystem?

pizza234 3 days ago | parent | prev [-]

Because the speed increase is - on modern, properly tuned filesystems - surprisingly small, due to how RDBMS's manage their pool; by working on large container files, they avoid most of the filesystem overhead.