From: Jeff King <peff@peff.net>
To: Dan McGee <dpmcgee@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 2/2] pack-objects: report actual number of threads to be used
Date: Sat, 4 Apr 2009 14:06:01 -0400 [thread overview]
Message-ID: <20090404180601.GA14888@coredump.intra.peff.net> (raw)
In-Reply-To: <1238864396-8964-2-git-send-email-dpmcgee@gmail.com>
On Sat, Apr 04, 2009 at 11:59:56AM -0500, Dan McGee wrote:
> In the case of a small repository, pack-objects is smart enough to not start
> more threads than necessary. However, the output to the user always reports
> the value of the pack.threads configuration and not the real number of
> threads to be used. This is easily fixed by moving the printing of the
> message after we have partitioned our work.
>
> (pack.threads is on autodetect and would be set to 4)
> $ git-repack -a -d -f
> Counting objects: 55, done.
> Delta compression using 2 threads.
> Compressing objects: 100% (48/48), done.
> Writing objects: 100% (55/55), done.
> Total 55 (delta 10), reused 0 (delta 0)
That makes sense to me, though I wonder if it may confuse and frustrate
users who are expecting their awesome quad-core machine to be using 4
threads when it only uses 2. Is it worth printing both values, or some
indicator that we could have been using more?
-Peff
next prev parent reply other threads:[~2009-04-04 18:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-04 16:59 [PATCH 1/2] git-repack: use non-dashed update-server-info Dan McGee
2009-04-04 16:59 ` [PATCH 2/2] pack-objects: report actual number of threads to be used Dan McGee
2009-04-04 18:06 ` Jeff King [this message]
2009-04-04 18:20 ` Dan McGee
2009-04-04 23:25 ` Jeff King
2009-04-05 0:11 ` Nicolas Pitre
2009-04-06 2:09 ` Dan McGee
2009-04-06 2:31 ` Nicolas Pitre
2009-04-06 2:34 ` Dan McGee
2009-04-06 3:14 ` Nicolas Pitre
2009-04-08 6:30 ` Junio C Hamano
2009-04-09 15:45 ` [PATCH] Update delta compression message to be less misleading Dan McGee
2009-04-11 19:24 ` Junio C Hamano
2009-04-11 19:42 ` Dan McGee
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=20090404180601.GA14888@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=dpmcgee@gmail.com \
--cc=git@vger.kernel.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 NNTP newsgroup(s).