public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Joel Joonatan Kaartinen <joel.kaartinen@gmail•com>
To: Ian Miers <imiers1@jhu•edu>
Cc: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] performance testing for bitcoin
Date: Thu, 04 Oct 2012 12:55:54 +0300	[thread overview]
Message-ID: <1349344554.31175.6.camel@mei> (raw)
In-Reply-To: <CAEC9zAZR7xOUEJZz0f-Of0HTVAcL8uCw3tcR1s66Hg_kZbczRg@mail.gmail.com>

For script evaluation benchmarking, I don't think just a good
approximation of real-world traffic is enough. You really need to
benchmark the worst case scenarios, otherwise you could be creating a
DoS vulnerability.

- Joel

ke, 2012-10-03 kello 13:57 -0400, Ian Miers kirjoitti:
> Script evaluation performance was what I was primarily concerned
> with.  I'm fooling around with adding some new instruction types.
> The tricky part is that to test how that effects performance, you need
> to be able to intersperse transactions with the new instructions with
> existing ones.  For accuracy, you'd like your simulated traffic to at
> least approximate the real world traffic.
> 
> 
> 
> 
> Also, is there any bench-marking / instrumentation in bitcoind ? 
> 
> 
> Ian
> On Wed, Oct 3, 2012 at 1:43 PM, Jeff Garzik <jgarzik@exmulti•com>
> wrote:
>         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
> 
> 
> ------------------------------------------------------------------------------
> Don't let slow site performance ruin your business. Deploy New Relic APM
> Deploy New Relic app performance management and know exactly
> what is happening inside your Ruby, Python, PHP, Java, and .NET app
> Try New Relic at no cost today and get our sweet Data Nerd shirt too!
> http://p.sf.net/sfu/newrelic-dev2dev
> _______________________________________________ Bitcoin-development mailing list Bitcoin-development@lists•sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development





  reply	other threads:[~2012-10-04  9:56 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
2012-10-03 17:43     ` Jeff Garzik
2012-10-03 17:57       ` Ian Miers
2012-10-04  9:55         ` Joel Joonatan Kaartinen [this message]
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=1349344554.31175.6.camel@mei \
    --to=joel.kaartinen@gmail$(echo .)com \
    --cc=bitcoin-development@lists$(echo .)sourceforge.net \
    --cc=imiers1@jhu$(echo .)edu \
    /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