user/dev discussion of public-inbox itself
 help / color / mirror / Atom feed
* what storage system(s) are you using?
@ 2020-08-05  3:11 Eric Wong
  2020-08-06 17:32 ` Konstantin Ryabitsev
  0 siblings, 1 reply; 3+ messages in thread
From: Eric Wong @ 2020-08-05  3:11 UTC (permalink / raw)
  To: meta

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).

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2020-08-21 18:51 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-08-05  3:11 what storage system(s) are you using? Eric Wong
2020-08-06 17:32 ` Konstantin Ryabitsev
2020-08-21 18:51   ` Eric Wong

user/dev discussion of public-inbox itself

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://public-inbox.org/meta
	git clone --mirror http://czquwvybam4bgbro.onion/meta
	git clone --mirror http://hjrcffqmbrq6wope.onion/meta
	git clone --mirror http://ou63pmih66umazou.onion/meta

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V1 meta meta/ https://public-inbox.org/meta \
		meta@public-inbox.org
	public-inbox-index meta

Example config snippet for mirrors.
Newsgroups are available over NNTP:
	nntp://news.public-inbox.org/inbox.comp.mail.public-inbox.meta
	nntp://ou63pmih66umazou.onion/inbox.comp.mail.public-inbox.meta
	nntp://czquwvybam4bgbro.onion/inbox.comp.mail.public-inbox.meta
	nntp://hjrcffqmbrq6wope.onion/inbox.comp.mail.public-inbox.meta
	nntp://news.gmane.io/gmane.mail.public-inbox.general
 note: .onion URLs require Tor: https://www.torproject.org/

code repositories for the project(s) associated with this inbox:

	https://80x24.org/public-inbox.git

AGPL code for this site: git clone https://public-inbox.org/public-inbox.git