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 ) 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 ; 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 (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 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: In-Reply-To: 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: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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.