From: Mike Hearn <mike@plan99•net>
To: "Jorge Timón" <jtimon@monetize•io>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Timed testing
Date: Thu, 17 Apr 2014 17:49:40 +0200 [thread overview]
Message-ID: <CANEZrP3s9SpBWxLYMvF5cLK4UeKS2SdKOLpNr40NKGoAzh=3nw@mail.gmail.com> (raw)
In-Reply-To: <CAC1+kJPvzxsSDg3joraZbv_r1RroK9d6-v9O_15g6S7B46TwQg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 294 bytes --]
>
> 2) If I wanted to measure validation performance, to get the number of
> peak tps that could be processed without taking block sides or network
> latency into account, how would I do that? Has anybody tried this
> before?
You can just reindex/replay the chain. It's been done many times.
[-- Attachment #2: Type: text/html, Size: 529 bytes --]
next prev parent reply other threads:[~2014-04-17 15:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-17 12:25 Jorge Timón
2014-04-17 13:00 ` Gavin Andresen
2014-04-17 15:11 ` Jorge Timón
2014-04-17 15:49 ` Mike Hearn [this message]
2014-04-17 16:09 ` Jorge Timón
2014-04-17 17:07 ` Gavin Andresen
2014-04-17 17:43 ` Jorge Timón
2014-04-17 16:35 ` Mark Friedenbach
2014-04-17 14:37 ` Brian Hoffman
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='CANEZrP3s9SpBWxLYMvF5cLK4UeKS2SdKOLpNr40NKGoAzh=3nw@mail.gmail.com' \
--to=mike@plan99$(echo .)net \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=jtimon@monetize$(echo .)io \
/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