From: Dave Hansen <haveblue@us.ibm.com>
To: "Martin J. Bligh" <mbligh@aracnet.com>
Cc: Dave Jones <davej@codemonkey.org.uk>,
Anton Blanchard <anton@samba.org>,
Jeff Garzik <jgarzik@pobox.com>, Andrew Morton <akpm@digeo.com>,
linux-kernel@vger.kernel.org, cliffw@osdl.org, akpm@zip.com.au,
slpratt@austin.ibm.com, levon@movementarian.org
Subject: Re: [PATCH] documentation for basic guide to profiling
Date: Sat, 01 Mar 2003 13:33:28 -0800 [thread overview]
Message-ID: <3E612728.6040707@us.ibm.com> (raw)
In-Reply-To: 3200000.1046552148@[10.10.2.4]
Martin J. Bligh wrote:
>>--start implies starting the daemon if it isn't started
>>already.
>
> I think John suggested to do those seperately, to minimise overhead
> or something.
On a heavily loaded system, --start can take quite a while if the daemon
isn't already running. Before starting my machine-killing benchmark
(which I want to profile), I use --start-daemon which gets most of the
work out of the way. The subsequent --start, which occurs while the
benchmark is already steaming along, will happen quickly and with much
less impact to the benchmark results.
--
Dave Hansen
haveblue@us.ibm.com
next prev parent reply other threads:[~2003-03-01 21:24 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-28 8:12 [PATCH] documentation for basic guide to profiling Martin J. Bligh
2003-02-28 8:29 ` Andrew Morton
2003-02-28 11:22 ` Dave Jones
2003-02-28 15:28 ` Jeff Garzik
2001-01-01 5:27 ` Anton Blanchard
2003-02-28 22:43 ` Martin J. Bligh
2003-02-28 23:05 ` Dave Hansen
2003-02-28 23:11 ` Martin J. Bligh
2003-03-01 17:51 ` Dave Jones
2003-03-01 20:48 ` John Levon
2003-03-02 23:05 ` Dave Jones
2003-03-01 20:55 ` Martin J. Bligh
2003-03-01 21:33 ` Dave Hansen [this message]
2003-03-03 21:57 ` Pavel Machek
2003-02-28 17:36 ` Randy.Dunlap
2003-02-28 18:11 ` Martin J. Bligh
2003-02-28 18:13 ` Dave Hansen
2003-02-28 19:30 ` Randy.Dunlap
2003-02-28 21:45 ` Martin J. Bligh
2003-02-28 21:49 ` Andries Brouwer
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=3E612728.6040707@us.ibm.com \
--to=haveblue@us.ibm.com \
--cc=akpm@digeo.com \
--cc=akpm@zip.com.au \
--cc=anton@samba.org \
--cc=cliffw@osdl.org \
--cc=davej@codemonkey.org.uk \
--cc=jgarzik@pobox.com \
--cc=levon@movementarian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@aracnet.com \
--cc=slpratt@austin.ibm.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.