-
Notifications
You must be signed in to change notification settings - Fork 99
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Benchmark tracking #1
Comments
3e92fa9f1be80575f1e5a0b1617a75b04805f152 on my development machine
|
Binary hash (width 3):
Circuit constraints (ARITY = 2): https://github.com/filecoin-project/neptune/blob/615ec19c3570a4c4e268273115bc8535db2b20ca/src/circuit.rs#L282 |
Perf regression might be related to benchmark. We're now computing (rather than just loading) constants on first access, and benchmark may be including this time. [UPDATE: benchmark was actually run with arity 2, although the commit shown is arity 8. That setting change for comparison wasn't committed.]
|
GPU:
|
Latest number with pure OpenCL implementation are reported here: #78 (comment) |
Issue for tracking benchmarks over time.
The text was updated successfully, but these errors were encountered: