-
Notifications
You must be signed in to change notification settings - Fork 44
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
code parameters do not give correct memory usage #2
Comments
oh, and it gets even worse if i let it go to the next iteration, so we must not be keeping track of memory very well:
|
This reference implementation is not optimized for memory at all. For the most efficient version please refer to https://github.com/xenoncat/equihash-xenon |
ok, thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
from the paper, n=144, k=5, should require 704 MB of memory, but the code does something terrifying on my linux box here. it says it will take 1.56GB, and then goes on to take somewhere between 5 and 6 GB of memory. also, due to how memory is handled/requested, this crashes my other computer (with only 8GB of memory, maybe it's running out of swap):
The text was updated successfully, but these errors were encountered: