public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: Adolf Belka <adolf.belka@ipfire.org>
Cc: Matthias Fischer <matthias.fischer@ipfire.org>,
	"IPFire: Development-List" <development@lists.ipfire.org>
Subject: Re: GIT is down...
Date: Sun, 14 Sep 2025 10:34:44 +0100	[thread overview]
Message-ID: <3076F215-4F2B-4BE9-9021-451FC36D2D6F@ipfire.org> (raw)
In-Reply-To: <4bc8479b-df45-41e1-ad27-99875620ed27@ipfire.org>

Hello everyone,

I have added a ton of caching to this over the last months. It really helps, but it cannot produce any wonders.

git.ipfire.org <http://git.ipfire.org/> is pushing out over 2 TiB of data every month. Doesn’t sound a lot, but for so tiny HTML pages, that is a lot of requests. There is a large cache in front of the gitweb CGI scripts, but the crawlers barely come back to visit the same page again so it does not help too much with the bot requests. It does however help us really well with the regular clients because the index page, summary page of the individual repositories and even the latest commits are all coming from the cache.

If anyone has any other ideas how to improve this all, please let me know.

-Michael

> On 14 Sep 2025, at 09:42, Adolf Belka <adolf.belka@ipfire.org> wrote:
> 
> Hi Matthias,
> 
> On 14/09/2025 10:28, Matthias Fischer wrote:
>> Good morning,
>> sorry to say, GIT (git.ipfire.org) is down.
>> ***SNIP***
>> Oops, Something Went Wrong
>> 503 ‐ Service Unavailable
>> ***SNAP***
> 
> No it is up nut it is being heavily crawled by bots again and this is basically causing a DoS.
> 
> You just have to wait for the crawling to ease off. It is frustrating though but not so easy to block. That is the internet for you these days.
> 
> Regards,
> 
> Adolf.
> 
>> Best
>> Matthias
> 
> 



      reply	other threads:[~2025-09-14  9:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-14  8:28 Matthias Fischer
2025-09-14  8:42 ` Adolf Belka
2025-09-14  9:34   ` Michael Tremer [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

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

  git send-email \
    --in-reply-to=3076F215-4F2B-4BE9-9021-451FC36D2D6F@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --cc=adolf.belka@ipfire.org \
    --cc=development@lists.ipfire.org \
    --cc=matthias.fischer@ipfire.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