3 ms·
Disk I/O is a huge limiting factor in a filesystem based approach to data persistence. Using a database for the persistence of data allows the db to schedule f
by ismarc 17y ago
Disk I/O is a huge limiting factor in a filesystem based approach to data persistence. Using a database for the persistence of data allows the db to schedule flushing the state to disk, independent of the actual requests. The situation you're specifically talking about, where there's nothing but static pages, there's no point in using a framework that's designed around building dynamic pages. You could just as easily write/use a templating system that takes content files and generates the HTML files from that content, and just run it when you have new content.
- prewett 17y agoWouldn't disk I/O be equally bad for a database? I assume the database gets cached in memory (as much as possible), but I would think that the file cache would have the same effect.
- ismarc 17y agoThe database can make all the disk I/O operations asynchronous because it provides an interface on top of file system itself. What you had listed would require either your own implementation (which you'd be better off using existing DB/Berkeley DB systems) of similar functionality, or actual disk I/O.