git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Steffen Prohaska <prohaska@zib.de>
Cc: John Keeping <john@keeping.me.uk>,
	Junio C Hamano <gitster@pobox.com>,
	Git Mailing List <git@vger.kernel.org>,
	Scott Chacon <schacon@gmail.com>
Subject: Re: [PATCH v2 2/2] convert: Stream from fd to required clean filter instead of mmap
Date: Sun, 17 Aug 2014 03:27:47 -0400	[thread overview]
Message-ID: <20140817072746.GD23808@peff.net> (raw)
In-Reply-To: <FA3F1197-25C5-42E4-9418-1C821D430819@zib.de>

On Sat, Aug 16, 2014 at 06:26:08PM +0200, Steffen Prohaska wrote:

> > Is the 15MB limit supposed to be imposed somewhere or is it just a guide
> > of how much memory we expect Git to use in this scenario?
> 
> The test should confirm that the the file that is added is not mmapped
> to memory.  The process size should be relatively small independently
> of the size of the file that is added.  I wanted to keep the file size
> small.  The chosen sizes worked for me on Mac and Linux.

Measuring memory usage seems inherently a bit flaky for the test suite.
It's also a little out of place, as the test suite is generally about
correctness and outcomes, and this is a performance issue.

Would it make more sense to construct a t/perf test that shows off the
change? I suppose the run-time change may not be that impressive, but it
would be cool if t/perf could measure max memory use, too. Then we can
just compare results between versions, which is enough to detect
regressions.

There's some prior art in the jk/pack-bitmap-reuse-deltas series (which
is not merged), where I taught it to measure output sizes of commands.
That should provide the necessary refactoring base, I think.

-Peff

  parent reply	other threads:[~2014-08-17  7:27 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-06  5:32 [PATCH v2 0/2] Stream fd to clean filter Steffen Prohaska
2014-08-06  5:32 ` [PATCH v2 1/2] convert: Refactor would_convert_to_git() to single arg 'path' Steffen Prohaska
2014-08-06  5:32 ` [PATCH v2 2/2] convert: Stream from fd to required clean filter instead of mmap Steffen Prohaska
2014-08-16 10:27   ` John Keeping
2014-08-16 16:26     ` Steffen Prohaska
2014-08-16 17:00       ` Andreas Schwab
2014-08-17 10:08         ` Steffen Prohaska
2014-08-17 11:03           ` Andreas Schwab
2014-08-17  7:27       ` Jeff King [this message]
2014-08-17 10:25         ` Steffen Prohaska
2014-08-17 11:33           ` Duy Nguyen
2014-08-19  7:53             ` Jeff King
2014-08-19  8:26               ` Steffen Prohaska

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=20140817072746.GD23808@peff.net \
    --to=peff@peff.net \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=john@keeping.me.uk \
    --cc=prohaska@zib.de \
    --cc=schacon@gmail.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).