Skip to content
This repository has been archived by the owner on Apr 19, 2022. It is now read-only.

Optimize equihash implementation #65

Merged
merged 2 commits into from Mar 29, 2019
Merged

Conversation

svyatonik
Copy link
Contributor

This is the first part of #64 . I've eliminated some allocations + extra loops && measured performance. The test was running verify_equihash_solution_works for 1000 times. Here are some results:

  1. old version of parity-zcash Equihash: 0.02655900600075256 secs / 1000 runs;
  2. librustzcash Equihash: 0.01449104799394263 secs / 1000 runs;
  3. new version of parity-zcash Equihash: 0.010416991004603915 secs / 1000 runs.

So the new implementation is ~61% faster than the previous one && ~28% faster than the librustzcash. q.e.d.

@svyatonik svyatonik merged commit 687e71c into master Mar 29, 2019
@svyatonik svyatonik deleted the equihash_optimization1 branch March 29, 2019 12:02
@wkarshat
Copy link

@svyatonik great improvements.
Would help to spec model and speed of the CPU and RAM used in testing, to calibrate expectations.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants