From: Ian Miers <imiers1@jhu•edu>
To: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] performance testing for bitcoin
Date: Wed, 3 Oct 2012 13:38:13 -0400 [thread overview]
Message-ID: <CAEC9zAbkWWcn5eRHLh6u+zyGu92E1Yq-9CQVPqE_6-QwMVs=4Q@mail.gmail.com> (raw)
In-Reply-To: <CAEC9zAYrMHHEyyTx1QVHoGSJU3fFypB0Hx4K-VFoUn0hp4Z7JA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 836 bytes --]
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).
At least in theory, one possibility would be to replay real
bitcoin transactions to a test-net-in-a-box network (of maybe a few nodes)
that has the real blockchain history loaded into it but then operates at a
far reduced hash difficulty in order facilitate running quickly.
Are there existing techniques/scripts for some kind of perf testing with
traffic that at least approximates real world traffic ?
The test infrastructure that ships with bitcoin does not appear to provide
this.
Thanks,
Ian
>
>
[-- Attachment #2: Type: text/html, Size: 1084 bytes --]
next parent reply other threads:[~2012-10-03 17:38 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 ` Ian Miers [this message]
2012-10-03 17:43 ` Jeff Garzik
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='CAEC9zAbkWWcn5eRHLh6u+zyGu92E1Yq-9CQVPqE_6-QwMVs=4Q@mail.gmail.com' \
--to=imiers1@jhu$(echo .)edu \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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