From: Eric Wong <e@80x24.org>
To: meta@public-inbox.org
Subject: Re: [PATCH 1/2] viewvcs: parallelize commit display
Date: Mon, 12 Feb 2024 19:58:16 +0000 [thread overview]
Message-ID: <20240212195816.M307182@dcvr> (raw)
In-Reply-To: <20240212131350.3443394-2-e@80x24.org>
Eric Wong <e@80x24.org> wrote:
> times down to ~6s (still slow). Avoiding patch generation for
> root commits (like cgit also does) brings it down to a few
> hundred milliseconds on a public-facing server.
Actually, the "(like cgit also does)" bit is wrong: cgit
generates a full patch, 355MB worth of HTML!
I got mixed up since I was testing cgit via shell script and set
QUERY_STRING incorrectly :x.
In any case, a 355MB HTML file isn't useful for anything but a
DoS attack against clients.
next prev parent reply other threads:[~2024-02-12 19:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-12 13:13 [PATCH 0/2] viewvcs improvements Eric Wong
2024-02-12 13:13 ` [PATCH 1/2] viewvcs: parallelize commit display Eric Wong
2024-02-12 19:58 ` Eric Wong [this message]
2024-02-12 13:13 ` [PATCH 2/2] viewvcs: HTML fixes for commits Eric Wong
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=20240212195816.M307182@dcvr \
--to=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).