1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <mark@monetize.io>) id 1WapI9-00083J-GV
for bitcoin-development@lists.sourceforge.net;
Thu, 17 Apr 2014 16:36:01 +0000
Received: from mail-pa0-f43.google.com ([209.85.220.43])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1WapI8-0006Ou-6m
for bitcoin-development@lists.sourceforge.net;
Thu, 17 Apr 2014 16:36:01 +0000
Received: by mail-pa0-f43.google.com with SMTP id bj1so551186pad.30
for <bitcoin-development@lists.sourceforge.net>;
Thu, 17 Apr 2014 09:35:54 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:message-id:date:from:organization:user-agent
:mime-version:to:subject:references:in-reply-to:content-type
:content-transfer-encoding;
bh=cYfmz3hnO+XTwm0y76K7O4+1cGqd5JamUm6MiFzrjmU=;
b=TDuyO928yF+cg0LplgnI0WSUJ0vj2ScLrmW1GWbt7HnKoQSBati8OOMj0lL1eHZ5xe
DA6bCY8nwaljTLUmM9tEw1myC5qo7wCGc4v8rHoCym7fjLQ3KuzuFAmMGTPGkR9GXd56
0Kpu9edzS0E//qgUDJdOXdL5U2zxY2J5lxt9UkT2OamOgBoz1/cnH37hd3uymgSL17Et
sjLhYIKFxyD9/7zTSxeYdIriBULqbRv5RevzvsSdPMn0LKvrk2FLjHnjAdENSjQVDM2O
74NYALod02ByUVtperBixPZFVzhKBHpMxFWWQwa0uAk75UW+IBsEXPR9ccvxAbdsb4Sx
h+eQ==
X-Gm-Message-State: ALoCoQmI7XdvB35ilMmfgopBQRBQDCl/NDo58x69mbFLMwCKnNc8wpHv1ca4PMAe9TOE7LTfAS33
X-Received: by 10.68.161.101 with SMTP id xr5mr10168966pbb.168.1397752554162;
Thu, 17 Apr 2014 09:35:54 -0700 (PDT)
Received: from [192.168.127.212] (50-0-36-93.dsl.dynamic.sonic.net.
[50.0.36.93])
by mx.google.com with ESMTPSA id y4sm54490985pbk.76.2014.04.17.09.35.52
for <bitcoin-development@lists.sourceforge.net>
(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
Thu, 17 Apr 2014 09:35:53 -0700 (PDT)
Message-ID: <535002E8.5020107@monetize.io>
Date: Thu, 17 Apr 2014 09:35:52 -0700
From: Mark Friedenbach <mark@monetize.io>
Organization: Monetize.io Inc.
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: bitcoin-development@lists.sourceforge.net
References: <CAC1+kJMrpx0tyE8d0wkwjBthhSPMCdr=9LrJHQFTF4G1vg4MAg@mail.gmail.com> <CABsx9T1HGwozy8pY+iStGZPmjenu0RQBVdtOy5ibiWG0BM4mZw@mail.gmail.com> <CAC1+kJPvzxsSDg3joraZbv_r1RroK9d6-v9O_15g6S7B46TwQg@mail.gmail.com>
<CANEZrP3s9SpBWxLYMvF5cLK4UeKS2SdKOLpNr40NKGoAzh=3nw@mail.gmail.com>
In-Reply-To: <CANEZrP3s9SpBWxLYMvF5cLK4UeKS2SdKOLpNr40NKGoAzh=3nw@mail.gmail.com>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
X-Headers-End: 1WapI8-0006Ou-6m
Subject: Re: [Bitcoin-development] Timed testing
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Thu, 17 Apr 2014 16:36:01 -0000
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.
|
