From: Andi Kleen <ak@linux.intel.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Andi Kleen <andi@firstfloor.org>, git@vger.kernel.org
Subject: Re: [PATCH 3/5] Run the perf test suite for profile feedback too
Date: Mon, 7 Jul 2014 15:15:07 -0700 [thread overview]
Message-ID: <20140707221507.GV19781@tassilo.jf.intel.com> (raw)
In-Reply-To: <xmqq1ttwdgjy.fsf@gitster.dls.corp.google.com>
On Mon, Jul 07, 2014 at 02:06:57PM -0700, Junio C Hamano wrote:
> Andi Kleen <andi@firstfloor.org> writes:
>
> > From: Andi Kleen <ak@linux.intel.com>
> >
> > Open: If the perf test suite is representative enough it may
> > be reasonable to only run that and skip the much longer full
> > test suite. Thoughts?
>
> I do not think it right now is representative, nor it was meant to
> become so. The operations are those that people cared about and
> tuned, and hopefully it would cover stuff actual end users care
> about in the real life, though.
I ended up answering the question by creating two separate
makefile targets in the next patch.
profile to run the full test suite and profile-fast to run
only the performance test. profile-fast as the name implies
is a lot faster to build, and fast enough that it's not
annoying.
I'll remove the "Open"
-Andi
next prev parent reply other threads:[~2014-07-07 22:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-04 23:43 Fix the bitrotted profile feedback build Andi Kleen
2014-07-04 23:43 ` [PATCH 1/5] Use BASIC_FLAGS for profile feedback Andi Kleen
2014-07-04 23:43 ` [PATCH 2/5] Don't define away __attribute__ on gcc Andi Kleen
2014-07-04 23:43 ` [PATCH 3/5] Run the perf test suite for profile feedback too Andi Kleen
2014-07-07 21:06 ` Junio C Hamano
2014-07-07 22:15 ` Andi Kleen [this message]
2014-07-04 23:43 ` [PATCH 4/5] Fix profile feedback with -jN and add profile-fast Andi Kleen
2014-07-04 23:43 ` [PATCH 5/5] Add a little script to compare two make perf runs Andi Kleen
2014-07-06 16:12 ` Bert Wesarg
2014-07-06 16:15 ` Andi Kleen
2014-07-06 16:46 ` Bert Wesarg
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=20140707221507.GV19781@tassilo.jf.intel.com \
--to=ak@linux.intel.com \
--cc=andi@firstfloor.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.