public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Mark Friedenbach <mark@monetize.io>
To: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Timed testing
Date: Thu, 17 Apr 2014 09:35:52 -0700	[thread overview]
Message-ID: <535002E8.5020107@monetize.io> (raw)
In-Reply-To: <CANEZrP3s9SpBWxLYMvF5cLK4UeKS2SdKOLpNr40NKGoAzh=3nw@mail.gmail.com>

Not necessarily. Running a private server involves listening to the p2p
network for incoming transactions, performing validation on receipt and
organizing a mempool, performing transaction selection, and relaying
blocks to auditors - none of which is tested in a reindex.

A reindex would give you an optimistic upper bound though, if that's all
you care about.

On 04/17/2014 08:49 AM, Mike Hearn wrote:
>     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. 



  parent reply	other threads:[~2014-04-17 16:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-17 12:25 [Bitcoin-development] Timed testing 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
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 [this message]
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=535002E8.5020107@monetize.io \
    --to=mark@monetize.io \
    --cc=bitcoin-development@lists.sourceforge.net \
    /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