Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 96FFA1BAA for ; Tue, 6 Oct 2015 21:00:10 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from sausage.cs.umd.edu (sausage.cs.umd.edu [128.8.127.43]) by smtp1.linuxfoundation.org (Postfix) with ESMTP id 591BC1DA for ; Tue, 6 Oct 2015 21:00:09 +0000 (UTC) Received: from mail-ob0-f176.google.com (mail-ob0-f176.google.com [209.85.214.176]) (Authenticated sender: amiller) by sausage.cs.umd.edu (Postfix) with ESMTPSA id D187E6C0EC7 for ; Tue, 6 Oct 2015 17:00:07 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=cs.umd.edu; s=csmx; t=1444165207; bh=RMkGoZhbp0RLAPaAz/35Ffj5dQU2oJZrboB2kJ1/s20=; h=In-Reply-To:References:Date:Subject:From:To:Cc; b=0++tMXGBvs/lnwQGw/5ifGSBu3TtISLrm99eAMuQR4KYxjYfmldmbI/Bnqmx5Hkkh eNAYELw08IZMrWBkPAa1+7/WHOBTWw3M3272h4SVtY1lElIwPnF7E+raqAvkh8eLEi QOcL8uFOXpRDrDJ4H4vIOIkL6dZHaDQRlQVYInvU= Received: by obcgx8 with SMTP id gx8so164205323obc.3 for ; Tue, 06 Oct 2015 14:00:07 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.60.118.137 with SMTP id km9mr2287331oeb.60.1444165207176; Tue, 06 Oct 2015 14:00:07 -0700 (PDT) Received: by 10.202.61.135 with HTTP; Tue, 6 Oct 2015 14:00:07 -0700 (PDT) Received: by 10.202.61.135 with HTTP; Tue, 6 Oct 2015 14:00:07 -0700 (PDT) In-Reply-To: References: Date: Tue, 6 Oct 2015 14:00:07 -0700 Message-ID: From: Andrew Miller To: naama.kates@gmail.com Content-Type: multipart/alternative; boundary=047d7b3a9bd02bc1c4052175eab3 X-Spam-Status: No, score=-4.3 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, HTML_MESSAGE, RCVD_IN_DNSWL_MED, T_RP_MATCHES_RCVD autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on smtp1.linux-foundation.org Cc: "bitcoin-dev@lists.linuxfoundation.org" Subject: Re: [bitcoin-dev] Bitcoin network simulation testing? X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Bitcoin Development Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Oct 2015 21:00:10 -0000 --047d7b3a9bd02bc1c4052175eab3 Content-Type: text/plain; charset=UTF-8 Shadow uses virtual time, entirely decoupled from real time. So while it may slow down your machine, this would not affect the stats collected (although it does make shadow somewhat unpleasant to run, unless you have a fast machine, compared to abstract simulators that avoid running the actual Bitcoin code). Hi Byron, I've been using shadow a bit-- I think these simulators are important for testing, but Shadow, at least, certainly seems to have limitations, in some crucial respects. Running shadow w Tor (which is only logical, because many BCT transactions transpire over Tor) is not as 'light' as presented and slows my own box down quite a bit, so the stats can't possibly be accurate... I don't know if this answers any questions or if you've had this experience at all -- perhaps it is negligible on a more powerful machine than my own-- or perhaps there is an adjustment still unaccounted? Regards, Nina K Sent from my iPhone On Oct 4, 2015, at 2:04 PM, Byron Gibson via bitcoin-dev < bitcoin-dev@lists.linuxfoundation.org> wrote: Hi all, is anyone using simulators like Shadow (https://shadow.github.io), BTCSim (https://github.com/btcsuite/btcsim), etc. to test proposed changes to Bitcoin? I have a few questions about their capabilities and limitations. Byron Gibson http://mirror.co/ https://keybase.io/byrongibson _______________________________________________ bitcoin-dev mailing list bitcoin-dev@lists.linuxfoundation.org https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev _______________________________________________ bitcoin-dev mailing list bitcoin-dev@lists.linuxfoundation.org https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev --047d7b3a9bd02bc1c4052175eab3 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Shadow uses virtual time, entirely decoupled from real time.= So while it may slow down your machine, this would not affect the stats co= llected

(although it does make shadow somewhat unpleasant to run, u= nless you have a fast machine,=C2=A0 compared to abstract simulators that a= void running the actual Bitcoin code).

Hi Byr= on,=C2=A0

I've been using shadow a bit-- I thi= nk these simulators are important for testing, but Shadow, at least, certai= nly seems to have limitations, in some crucial respects.=C2=A0 Running shad= ow w Tor (which is only logical, because many BCT transactions transpire ov= er Tor) is not as 'light' as presented and slows my own box down qu= ite a bit, so the stats can't possibly be accurate... I don't know = if this answers any questions or if you've had this experience at all -= - perhaps it is negligible on a more powerful machine than my own-- or perh= aps there is an adjustment still unaccounted?

Rega= rds,
Nina K

Sent from my iPhone

On Oc= t 4, 2015, at 2:04 PM, Byron Gibson via bitcoin-dev <bitcoin-dev@lists.l= inuxfoundation.org> wrote:

Hi all, is anyone using simulators like Shadow (https://shadow.github.io), BTCSim (https://github.com/btcsuite/btcsim), etc. to test proposed changes to= Bitcoin?=C2=A0 I have a few questions about their capabilities and limitat= ions.

Byron Gibson
http://mirror.co/
https://keybas= e.io/byrongibson

=C2=A0=C2=A0=C2=A0

___________________= ____________________________
bitcoin-dev mailing list
bitcoin-dev@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev=

_______________________________= ________________
bitcoin-dev mailing list
bitcoin-dev@lists.= linuxfoundation.org
https://lists.linuxfoundation.org/mail= man/listinfo/bitcoin-dev

--047d7b3a9bd02bc1c4052175eab3--