From: e at 80x24.org (Eric Wong)
Subject: [RFC] use buffered stdio (lightly tested)
Date: Sat, 5 Jan 2019 22:02:08 +0000 [thread overview]
Message-ID: <20190105220208.GA17849@dcvr> (raw)
In the future, I think it could be even more beneficial to
buffer to zlib (if the client accepts gzip) and bypass stdio
buffering in those cases. Smaller responses via gzip means less
IPC overhead and wakeups for the reader.
cgit is linked against zlib anyways because of git, so no extra
linkage, either. But we'll need uncompressed code paths anyways
for clients which don't support gzip.
prev parent reply other threads:[~2019-01-05 22:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-01 13:23 e
2019-01-02 9:16 ` e
2019-01-05 22:02 ` e [this message]
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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 NNTP newsgroup(s).