From: Jeff Garzik <jgarzik@exmulti.com>
To: Ian Miers <imiers1@jhu.edu>
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] performance testing for bitcoin
Date: Wed, 3 Oct 2012 13:43:36 -0400 [thread overview]
Message-ID: <CA+8xBpdZDznkyWXn8AxdUDk0CJ0b2m1qpTgVjtPbs0ge+ODCSg@mail.gmail.com> (raw)
In-Reply-To: <CAEC9zAbkWWcn5eRHLh6u+zyGu92E1Yq-9CQVPqE_6-QwMVs=4Q@mail.gmail.com>
On Wed, Oct 3, 2012 at 1:38 PM, Ian Miers <imiers1@jhu.edu> wrote:
> Whats the best way to get performance numbers for modifications to bitcoin ?
> Profiling it while running on testnet might work, but that would take a
> rather long time to get data.
> Is there anyway to speed this up if we only needed to provide relative
> performance between tests. (in a sense a fast performance regression test).
You have to be specific about what you're measuring, because
"performance" is vague.
You can measure many aspects of blockchain performance by importing
blocks via -loadblock=FILE.
Other performance measurements like "how fast does a block relay
through the network" cannot be as easily measured.
--
Jeff Garzik
exMULTI, Inc.
jgarzik@exmulti.com
next prev parent reply other threads:[~2012-10-03 17:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAEC9zAbHO9y7Go4FhZFyOCKdm1js_eKCoz7iaOCh1Wu=B9OASw@mail.gmail.com>
[not found] ` <CAEC9zAYrMHHEyyTx1QVHoGSJU3fFypB0Hx4K-VFoUn0hp4Z7JA@mail.gmail.com>
2012-10-03 17:38 ` [Bitcoin-development] performance testing for bitcoin Ian Miers
2012-10-03 17:43 ` Jeff Garzik [this message]
2012-10-03 17:57 ` Ian Miers
2012-10-04 9:55 ` Joel Joonatan Kaartinen
2012-10-04 16:31 ` Ian Miers
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=CA+8xBpdZDznkyWXn8AxdUDk0CJ0b2m1qpTgVjtPbs0ge+ODCSg@mail.gmail.com \
--to=jgarzik@exmulti.com \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=imiers1@jhu.edu \
/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