Is sequential IO dead in the era of the NVMe drive? — Jack Vanlightly
Two systems I know pretty well, Apache BookKeeper and Apache Kafka, were designed in the era of the spinning disk, the hard-drive or HDD. Hard-drives are good at sequential IO but not so good at random IO because of the relatively high seek times. No wonder then that both Kafka and BookKeeper were d
Image credit: ESO/A. Ghizzi Panizza (www.albertoghizzipanizza.com) Two systems I know pretty well, Apache BookKeeper and Apache Kafka, were designed in the era of the spinning disk, the hard-drive or HDD. Hard-drives are good at sequential IO but not so good at random IO because of the relatively high seek times. No wonder then that both Kafka and BookKeeper were designed with sequential IO in mind. Both Kafka and BookKeeper are distributed log systems and so you’d think that sequential IO would be the default for an append-only log storage system. But sequential and random IO sit on a continu
Explore this link on the map →related reading
- IO devices and latency — PlanetScaleplanetscale.com
- Log Structured Merge Trees | Ben Stopfordbenstopford.com
- Century-Scale Storagelil.law.harvard.edu
- What Every Programmer Should Know About Memorypeople.freebsd.org
- Building and operating a pretty big storage system called S3 | All Things Distributedallthingsdistributed.com
- NYSRGnotes.ekzhang.com
- Disks and Files - Database Systemscs186berkeley.net
- Are you a memory_man, Part 2 - by Investing with Martinmartinbradstreet.substack.com
- Build Your Own Databasenan.fyi
- Database Fundamentalstontinton.com
- k8s-1m Overviewbchess.github.io
- Buffer cache | CS 162 Project 3cs162.org