From: Eric Wong <e@80x24.org>
To: git@vger.kernel.org
Cc: meta@public-inbox.org
Subject: public-inbox.org/git/*/s/ endpoints struggling
Date: Sun, 7 Apr 2024 09:29:04 +0000 [thread overview]
Message-ID: <20240407092904.M799327@dcvr> (raw)
The blob reconstruction endpoints (aka the WWW version of `lei
blob') have been hammered by bots while I'm gathering data to
reproduce (and hopefully fix) fragmentation problems in
dlmalloc-based allocators. The data gathering is silly
expensive all around and I'm on old and slow hardware and
intentionally ramped up bot traffic to gather more data. I've
tweaked robots.txt for now, but it will take some time to take
effect and I'm also distracted with offline crap.
AFAIK, nobody else is running instances with blob reconstruction
enabled, yet (the feature has existed since 2019). It's a
PITA to configure but I've been doing extensive work to make it
easier to configure and use.
reply other threads:[~2024-04-07 9:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240407092904.M799327@dcvr \
--to=e@80x24.org \
--cc=git@vger.kernel.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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).