From: Eric Wong <e@yhbt.net>
To: meta@public-inbox.org
Subject: [PATCH 7/9] xt/git_async_cmp: do not slurp large OID list into memory
Date: Sat, 11 Jan 2020 22:35:01 +0000 [thread overview]
Message-ID: <20200111223503.24473-8-e@yhbt.net> (raw)
In-Reply-To: <20200111223503.24473-1-e@yhbt.net>
I somehow thought "foreach (<$cat>)" could work like
"while (<$cat>)" when it came to iterating over file
handles...
---
xt/git_async_cmp.t | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/xt/git_async_cmp.t b/xt/git_async_cmp.t
index f8ffe3d9..18fce3db 100644
--- a/xt/git_async_cmp.t
+++ b/xt/git_async_cmp.t
@@ -27,7 +27,7 @@ my $async = timeit($nr, sub {
my $cat = $git->popen(@cat);
$git->cat_async_begin;
- foreach (<$cat>) {
+ while (<$cat>) {
my ($oid, undef, undef) = split(/ /);
$git->cat_async($oid, $cb);
}
@@ -39,7 +39,7 @@ my $async = timeit($nr, sub {
my $sync = timeit($nr, sub {
my $dig = Digest::SHA->new(1);
my $cat = $git->popen(@cat);
- foreach (<$cat>) {
+ while (<$cat>) {
my ($oid, undef, undef) = split(/ /);
my $bref = $git->cat_file($oid);
$dig->add($$bref);
next prev parent reply other threads:[~2020-01-11 22:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-11 22:34 [PATCH 0/9] more small fixes and cleanups Eric Wong
2020-01-11 22:34 ` [PATCH 1/9] config: do not slurp entire cgitrc at once Eric Wong
2020-01-11 22:34 ` [PATCH 2/9] git: modified: don't slurp `rev-parse --branches' Eric Wong
2020-01-11 22:34 ` [PATCH 3/9] git: packed_bytes: use GLOB_NOSORT Eric Wong
2020-01-11 22:34 ` [PATCH 4/9] solver: path_a may be undef from /dev/null Eric Wong
2020-01-11 22:34 ` [PATCH 5/9] cgit: drop cgit_parse_hdr wrapper Eric Wong
2020-01-11 22:35 ` [PATCH 6/9] xapcmd: use popen_rd for running xapian-compact Eric Wong
2020-01-11 22:35 ` Eric Wong [this message]
2020-01-11 22:35 ` [PATCH 8/9] t/solver_git: avoid uninitialized warnings in hostname generation Eric Wong
2020-01-11 22:35 ` [PATCH 9/9] use popen_rd for bidirectional pipes 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: http://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=20200111223503.24473-8-e@yhbt.net \
--to=e@yhbt.net \
--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/public-inbox.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).