From: Jason at zx2c4.com (Jason A. Donenfeld)
Subject: RFC: don't cache objects larger than X
Date: Wed, 12 Oct 2016 13:22:34 +0200 [thread overview]
Message-ID: <CAHmME9p9V=etf2VX7szyFegOFZb1Bc=G-m3K00e0pwoGs+Kjgw@mail.gmail.com> (raw)
In-Reply-To: <20161010140312.GB2142@gmail.com>
I face this same problem, in fact. Unless somebody beats me to it, I'd
be interested in giving this a stab.
One issue is that cache entries are currently "streamed" into the
cache files, as they're produced. It's not trivially possible to know
how big it's going to be beforehand. This means that the best we could
do would be to just immediately unlink it after creation and printing.
Would this be acceptable?
Regards,
Jason
next prev parent reply other threads:[~2016-10-12 11:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-10 14:03 mricon
2016-10-12 11:22 ` Jason [this message]
2016-10-12 13:05 ` mricon
2016-10-17 17:56 ` lfleischer
2016-10-17 18:39 ` Jason
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='CAHmME9p9V=etf2VX7szyFegOFZb1Bc=G-m3K00e0pwoGs+Kjgw@mail.gmail.com' \
--to=cgit@lists.zx2c4.com \
/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 NNTP newsgroup(s).