geth 1.5 is way faster but there are problems to keep connections with peers. When there is a high latency, it removes agressively the peer connection. I use the patch 2630 from Péter Szilágyi in the 1.5 version.
benchmarks done on OS X with 37320qm 16Go ram 1To SSD with geth 1.4.4 (stable):
No benchmark looks to be available and i think it's due to the fact that this card looks to be very expensive and quantity is limited. However, the pro duo seems to be a radeon fury x2. So you can imagine that, as fury x looks to be around 30MH/s, this card would be 60MH/s. However for the same hashrate you can use 3 radeon r9 290 with some oc and it will ...
The simplest would be to try it your own.
use new Date().getTime()
The getTime() method returns the number of milliseconds since midnight of January 1, 1970.
First unlock your account: personal.unlockAccount(sender, password, time);
var start = new Date().getTime();
var amount = 1;
var sender = personal.listAccounts
I can't speak to the others as I work on Quorum, but there are a few good sources that our team uses and references.
Here is performance evaluation done by an external team with published method and results: https://arxiv.org/abs/1809.03421
Here is one of the tools we use that tries to standardize a way to submit and measure txn throughput in ethereum like ...
I did a few bench by myself and found as well that there is no significant impact of --jitvm. And I agree that geth 1.5.0 with patch is way faster.:)
Note: the 1.4.6 version has these patchs and synchronize quickly
I faced a similar problem a while ago, there was a bottleneck on the time it took transactions to reach the mempool, this was due to the way I was sending them and the fact that they were being signed at node level. That added a pretty big overhead.
The solution I found is to replicate a more real environment.
Sign all transactions locally (pre-signed them)...
I would suggest this.
Smart contract execution on EVM is effectively same as code execution on any (virtual) machine
For each transaction, you can trace what "CPU" instructions were executed
You can assign a cost for each instructions
If you want to do this in advanced way, you can for example use Intel performance tuning suites and a doctored Go Ethereum/...
For Geth v1.9.0, look here for some new details on sync time. Describes all three modes and times including some changes that one should know about.
As of Aug 2, 2019 the size on disk for me was 356 GB and state entries went to 370 million. Takes a couple of days to sync with a ssd drive. Be patient.
First the Ethereum blockchain is growing and growing at a faster pace. It would possibly reach 40Gb in no time. Thus allocating 1GB cache (cache--1024) is still not enough, but the syncing will go on, the time to sync depends on the following factors:
2. Power supply
3. Device specifications, Normally you need at least a 2Gb RAM, 256 Gb ...