user/dev discussion of public-inbox itself
 help / color / mirror / Atom feed
From: Eric Wong <e@yhbt.net>
To: meta@public-inbox.org
Subject: Re: what storage system(s) are you using?
Date: Fri, 21 Aug 2020 18:51:49 +0000
Message-ID: <20200821185149.GA15309@dcvr> (raw)
In-Reply-To: <20200806173237.jf7nrfbw5v7uvl5s@chatter.i7.local>

Konstantin Ryabitsev <konstantin@linuxfoundation.org> wrote:
> On Wed, Aug 05, 2020 at 03:11:27AM +0000, Eric Wong wrote:
> > I've been mostly using ext4 on SSDs since I started public-inbox
> > and it works well.
> 
> As you know, I hope to move lore.kernel.org to a system with a hybrid 
> lvm-cache setup, specifically:
> 
> 12 x 1.8TB rotational drives set up in a lvm raid-6 array
> 2  x 450GB SSD drives are lvm-cache volume
> 
> This gives up 18TB capacity with a 900GB cache layer, and the FS on top 
> of that is XFS.
> 
> This is what is currently serving mirrors.edge.kernel.org (4 nodes 
> around the world).

Do you have any numbers on read IOPS or seek latency for the
RAID-6 array?  Also, how much RAM for the page cache?

Xapian is going to be tricky(*), and it's looking like group search
will require a separate index :<  The upside is it may be able
to gradually replace existing indices for WWW and deduplicate
much data for cross-posted messages.

IMAP/JMAP is a different story...

Removing or relocating inboxes isn't going to be fun, either.

(*) Xapian built-in sharding works well for matching CPU core count,
    but trying to use Xapian's MultiDatabase (via ->add_database) with
    the current mirror of lore (almost 400 shards) doesn't work well,
    at all.

      reply	other threads:[~2020-08-21 18:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-05  3:11 Eric Wong
2020-08-06 17:32 ` Konstantin Ryabitsev
2020-08-21 18:51   ` Eric Wong [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://public-inbox.org/README

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200821185149.GA15309@dcvr \
    --to=e@yhbt.net \
    --cc=meta@public-inbox.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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