More like: 1.88/1.66 = 1.13 Sol/s. That it found 3 solutions for this particular nonce is pure luck and is mostly irrelevant to estimating the average solution rate.
The 2 sol/s was achieved with faster1 which uses a lot more memory. Once I fix the allocation bug, you will be able to reproduce it with
time ./fast1 -n 1000 -r 100
and dividing the total 188 solutions by the time taken.
OK; bug is fixed now…
OK. Meanwhile, on i7-4770K:
$ time ./equi1 -r 10
[...]
19 total solutions
real 0m12.640s
user 0m12.234s
sys 0m0.395s
18.8/12.6 = ~1.5 Sol/s.
4 threads:
real 0m5.836s
user 0m20.906s
sys 0m1.462s
8 threads:
real 0m3.837s
user 0m25.584s
sys 0m3.759s
18.8/3.8 = ~5 Sol/s. I haven’t yet tried separate instances on this CPU, but I expect those will perform slightly faster. I’ll stop at this for now, expecting that you’ll make improvements by the Challenge judging time. Thank you once again for open-sourcing this!
I don’t see myself seriously competing with those assembly/SIMD wizards:-(
But we’ll see…
Wow, that was quick. OK, here’s faster1 on the i7-4770K:
$ time ./faster1 -r 10
[...]
19 total solutions
real 0m10.328s
user 0m10.281s
sys 0m0.038s
18.8/10.3 = ~1.8 Sol/s
$ time ./faster -r 10 -t 8
[...]
19 total solutions
real 0m2.998s
user 0m21.577s
sys 0m0.404s
18.8/3.0 = ~6.3 Sol/s
Thanks for opensourcing @tromp
Is this just a equihash solver or can we run it against the testnet ?
Currently messing around with it.
Just a solver; needs some engineering to hook into zcashd…
Is there anyone working on incorporating your Solver into a Miner?
Yes; genoil is working on an openCL miner based on my solvers. But it’s up to him to decide what to do with it.
There’s also a good chance other contest competitors will end up writing miners based on mine and xenoncat’s solvers…
There was a 1.52337263 BTC donation of unknown origin. Could the contributor please identify themselves or contact me to discuss refunding?
I’ll be working this weekend on a branch of my standalone miner that can run as many of the submissions as I can get working there ![]()
@str4d Exciting! Can’t wait to try it out
@tromp Hold my small contribution to Cuckoo Cycle Bounty … and thanks to push your competence on this project … everything is happening too fast
And before anyone asks, a disclaimer:
Inclusion in my standalone miner has NO BEARING on any eventual judging by myself or the other judges.
That being said, miners that are able to be included into my standalone miner are inherently satisfying at least a few particular parts of the judging criteria (because my standalone miner uses the same build system and setup as zcashd). But again, don’t take this as any kind of premature endorsement.
And another disclaimer: it’s entirely possible that I’ll end up being swamped with work and not get any solvers included into my miner this weekend. So if anyone wants to have a go at it first, I’ll happily review a pull request to my miner ![]()
Hi tromp, thanks for open sourcing and kicking off this initiative - please keep my 1BTC donation to your cuckoo cycle bounty
Thanks so much, nethyb!
I’ve decided to bump up my Cuckoo Cycle bounties from a former total of $1500 to the current $5000.
I’d like to donate my 1 ⓑ (https://blockexplorer.com/tx/817c6f8e77ee9ecbda3764c36ae1b71a403640491586016b4bb8262d760a955b) to the Cuckoo bounty fund.
Much appreciated, zooko!
Having handled all contributors of >= 1BTC, today I will be contacting those contributing from 0.2 BTC up to 1 BTC