From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-Status: No, score=-4.0 required=3.0 tests=ALL_TRUSTED,AWL,BAYES_00 shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from localhost (dcvr.yhbt.net [127.0.0.1]) by dcvr.yhbt.net (Postfix) with ESMTP id 158841F990; Wed, 5 Aug 2020 03:11:28 +0000 (UTC) Date: Wed, 5 Aug 2020 03:11:27 +0000 From: Eric Wong To: meta@public-inbox.org Subject: what storage system(s) are you using? Message-ID: <20200805031127.GA11917@dcvr> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline List-Id: I've been mostly using ext4 on SSDs since I started public-inbox and it works well. 1.6.0 will have some changes to make things less slow on rotational HDDs (and even faster on SSD). It's still slow, just a bit less slow than before. Testing things on giant inboxes is like watching grass grow. Small inboxes that can fit into the page cache aren't too bad... I'm also evaluating btrfs since its raid1 is handy when I've got a bunch of old mismatched HDDs for backups. btrfs may become the default FS for Fedora (and maybe other distros will follow), so I anticipate we'll see more btrfs adoption as time goes on. Out-of-the-box, btrfs is not remotely suited for random write patterns from Xapian and SQLite. However it gives some extra piece-of-mind with checksumming and compresssion of git refs. Since we don't care much about data integrity of Xapian or SQLite data, 1.6.0 will set the nodatacow attribute on those files/directories: https://public-inbox.org/meta/20200728222158.17457-1-e@yhbt.net/ With the default CoW, even a TRIM-ed SSD was abysmal at indexing LKML. The space_cache=v2 mount option seems to help significantly with large, multi-TB FSes (still testing...). This will be noted in a public-inbox-tuning(7) manpage... I haven't done much with XFS outside of a VM. Since it doesn't have CoW, I expect it to be similar to ext4 as far as this codebase is concerned. From what I recall years ago, unlink(2) was slow on XFS with Maildirs, and it's also the case currently with btrfs... Another interesting bit: SQLite uses some F2FS-only APIs. So F2FS could be good for SSD users; but I've yet to try it... I also don't know if network filesystems (Ceph, Gluster, NFS, Lustre, AFS, ...) work at all. Maybe they're fine for git storage, but probably not with SQLite, Xapian or flock(2).