From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Eric Wong <e@80x24.org>
Cc: meta@public-inbox.org
Subject: Re: --batch-size and --jobs combination
Date: Thu, 5 Aug 2021 16:59:39 -0400 [thread overview]
Message-ID: <20210805205939.kpy6dixzjopbuhyx@nitro.local> (raw)
In-Reply-To: <20210805110541.GA6446@dcvr>
On Thu, Aug 05, 2021 at 11:05:41AM +0000, Eric Wong wrote:
> > - I will bring up the rest of the nodes throughout the week, so
> > x-lore.kernel.org will become more geoip-balanced. I will share any other
> > observations once I have more data. Once all 4 nodes are up, I will share
> > this more widely with kernel devs so they can kick some tires and report
> > whether they are seeing decreased performance compared to current
> > lore.kernel.org. It's entirely possible that my plan to use
> > mirrors.edge.kernel.org nodes for this isn't one of my brightest ideas, in
> > which case I may bring up several dedicated instances in multiple clouds
> > instead.
>
> Increasing the size of the SSD caches would net the most
> dramatic improvement (or going SSD-only). Even consumer grade
> SSDs (MLC/TLC) leave enterprise HDDs in the dust.
The more I poke at this, the more it seems that using faster storage is a much
better plan than trying to make this work reasonably well with our distro
mirroring nodes. Occasional high IO latency will go largely unnoticed when
it's apt or dnf that's fronting the requests, but web or b4 calls that make
someone wait for 10+ seconds seems like a recipe for some very irate
developers.
I actually have a good opportunity to move our current git.kernel.org systems
to newer hardware at Equinix Metal. We'll go from 6 older nodes to 3 newer
nodes, each with more CPU/RAM and 1.2TB total of SSD. This should give us
plenty of room to colocate lore.kernel.org on the same systems as
git.kernel.org, and it's a much better plan than trying to make spinning rust
work well for this purpose.
> > Thanks for all your work, Eric.
>
> You're welcome and thanks for the support. It's been a very
> rough time, especially with the pandemic still dragging on :<
And we thought we were all done this spring, eh? Ah well, this too shall pass.
Best regards,
-K
prev parent reply other threads:[~2021-08-05 20:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-29 20:28 --batch-size and --jobs combination Konstantin Ryabitsev
2021-07-29 21:13 ` Eric Wong
2021-07-29 21:24 ` Konstantin Ryabitsev
2021-07-29 22:06 ` Eric Wong
2021-08-01 20:40 ` Konstantin Ryabitsev
2021-08-05 11:05 ` Eric Wong
2021-08-05 20:59 ` Konstantin Ryabitsev [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=20210805205939.kpy6dixzjopbuhyx@nitro.local \
--to=konstantin@linuxfoundation.org \
--cc=e@80x24.org \
--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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).