From: Eric Voskuil <eric@voskuil•org>
To: Tamas Blummer <tamas@bitsofproof•com>,
Cory Fields <lists@coryfields•com>
Cc: bitcoin-dev@lists•linuxfoundation.org
Subject: Re: [bitcoin-dev] libconsensus assertion fails if used in multiple threads
Date: Tue, 18 Aug 2015 14:40:27 -0700 [thread overview]
Message-ID: <55D3A64B.3000103@voskuil.org> (raw)
In-Reply-To: <68E206FF-4ABD-4547-BF73-8661A7C2F08B@bitsofproof.com>
[-- Attachment #1: Type: text/plain, Size: 484 bytes --]
On 08/18/2015 03:31 AM, Tamas Blummer via bitcoin-dev wrote:
> The performance of libconsensus is surprisingly close to the java one.
...
> Another nice demonstration why one should not trade in advances
> of languages for the last decades for a marginal gain of performance
> with C/C++...
If performance was the only trade-off with Java, and if C++ was frozen
in time, I would say you have a point.
Thanks for submitting, and Cory, thanks for working this out.
e
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2015-08-18 21:42 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-14 9:59 [bitcoin-dev] Adjusted difficulty depending on relative blocksize Jakob Rönnbäck
2015-08-14 13:32 ` Angel Leon
2015-08-14 14:19 ` Jakob Rönnbäck
2015-08-14 16:37 ` [bitcoin-dev] libconsensus assertion fails if used in multiple threads Tamas Blummer
2015-08-14 21:10 ` Cory Fields
2015-08-18 5:03 ` Cory Fields
2015-08-18 10:31 ` Tamas Blummer
2015-08-18 17:25 ` Cory Fields
2015-08-18 17:50 ` Cory Fields
2015-08-18 21:40 ` Eric Voskuil [this message]
2015-08-14 14:20 ` [bitcoin-dev] Adjusted difficulty depending on relative blocksize Anthony Towns
[not found] ` <A6B32C22-4006-434E-9B89-D7C99B5743A8@me.com>
2015-08-14 14:48 ` Jakob Rönnbäck
2015-08-14 15:00 ` Anthony Towns
2015-08-14 15:03 ` Adam Back
2015-08-14 15:14 ` Jakob Rönnbäck
2015-09-09 3:27 ` Tom Harding
2015-09-09 18:59 ` Warren Togami Jr.
2015-09-09 19:53 ` Tom Harding
2015-08-14 22:12 ` Tom Harding
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=55D3A64B.3000103@voskuil.org \
--to=eric@voskuil$(echo .)org \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=lists@coryfields$(echo .)com \
--cc=tamas@bitsofproof$(echo .)com \
/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