Conversation

Notices

1. Embed this notice
   Eaton (eaton@phire.place)'s status on Saturday, 12-Oct-2024 05:47:46 JST Eaton

   in reply to

   • Deane Barker

   @deane As long as you’ve got a straightforward and unambiguous mapping between “what is requested” and “what’s the pathname”, yeah, modern SSDs really ARE database-fast. It’s wild!

   • Embed this notice
     Deane Barker (deane@contenttechtodon.org)'s status on Saturday, 12-Oct-2024 05:47:48 JST Deane Barker

     in reply to

     I used to cache this. Like, I had this big caching architecture to avoid these file reads. It was complicated and invalidation was a mess.

     When I realize just how damn fast the file system actually was, I deleted HUNDREDS of lines of code -- like, multiple classes and background services.

     It was heavenly.

   • Embed this notice
     Deane Barker (deane@contenttechtodon.org)'s status on Saturday, 12-Oct-2024 05:47:49 JST Deane Barker

     in reply to

     I have a process that does multiple reads for every inbound request. It searches the file system for filenames of a particular pattern, then reads multiple files in.

     This takes, on average, 3 milliseconds.

   • Embed this notice
     Deane Barker (deane@contenttechtodon.org)'s status on Saturday, 12-Oct-2024 05:47:50 JST Deane Barker

     I think we're underestimating how fast SSD file systems can be. Using C#, my desktop machine can read in the entire text of "War and Peace" from a 3.2MB text file in 6 milliseconds.

     That's database-ish fast.