-
Notifications
You must be signed in to change notification settings - Fork 84
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
Performance ideas #12
Comments
Use mine :-) 371 K/s/Core - Used settings = 6 Cores - 6 * 371 * 60 * 60 * 24 = 192.326.400 addresses / day = 70.199.136.000 addresses / year |
|
You have to fill you're DB with all the addresses you want to check. This script uses the UPDATE query for all generated addresses. When an address exist => it will put the secret key in the DB. If the generated address is not present in your DB: nothing happens. |
Hi |
@cabanu My program modification with set() gives me 540K/s * core on a raspi. 540 K/s * Core - Used settings = 4 Cores - 4 * 540 * 60 * 60 * 24 = 186.624.000 addresses / day = 68.117.760.000 addresses / year |
So the primary throttle is searching the bits.txt file. Use a much larger file, and the rate drops very low.
Might I suggest each CPU thread writes to a DB (mongo/memcache/redis/mysql), then other threads can search for matches and delete when no match is found?
The text was updated successfully, but these errors were encountered: