From: naama.kates@gmail•com
To: Byron Gibson <byron@mirror•co>
Cc: "bitcoin-dev@lists•linuxfoundation.org"
<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Bitcoin network simulation testing?
Date: Tue, 6 Oct 2015 13:14:28 -0700 [thread overview]
Message-ID: <E8AC44C1-310F-44AE-AB5E-63064A3DE1BE@gmail.com> (raw)
In-Reply-To: <CAOVG1oNimYpzSnB7NUuugagufbD1JnZmAWsuXhMjq45dEF=w-g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1260 bytes --]
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
[-- Attachment #2: Type: text/html, Size: 2053 bytes --]
next prev parent reply other threads:[~2015-10-06 20:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-04 21:04 Byron Gibson
2015-10-06 20:14 ` naama.kates [this message]
2015-10-06 21:00 ` Andrew Miller
2015-10-09 17:11 ` Byron Gibson
2015-10-09 22:06 ` Pindar Wong
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=E8AC44C1-310F-44AE-AB5E-63064A3DE1BE@gmail.com \
--to=naama.kates@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=byron@mirror$(echo .)co \
/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