Skip to content

speed in xpoint mode #128

Closed
Closed
@albertobsd

Description

Guys someone else is having issues with the xpoint mode?

It was reported it #111 by @Gusev39rus

user@AMD:~/Рабочий стол/keyhunt$ ./keyhunt -m xpoint -f tests/120_rec.txt -t 128 -r 0:5AF3107A4000

[+] **Version 0.2.211012 Chocolate ¡Beta!, developed by AlbertoBSD**
[+] Mode xpoint
[+] Threads : 128
[+] Opening file tests/120_rec.txt
[+] Allocating memory for 8000000001 elements: 152587.89 MB
[+] Bloom filter for 8000000001 elements.
[+] Loading data to the bloomfilter total: 27423.07 MB
[+] Bloomfilter completed
[+] Sorting data ... done! 8000000001 values were loaded and sorted
^Cse key: 1f01f12be2      in 4230 seconds: **974952 keys/s**

user@AMD:~/Рабочий стол/keyhunt_old$ ./keyhunt -m xpoint -f tests/120_rec.txt -t 128 -r 0:5AF3107A4000
[+] **Version 0.1.20210412 secp256k1**
[+] Setting mode xpoint
[+] Setting 128 threads
[+] Opening file tests/120_rec.txt
[+] Allocating memory for 8000000001 elements: 152587.89 MB
[+] Initializing bloom filter for 8000000001 elements.
[+] Loading data to the bloomfilter total: 22852.56 MB
[+] Bloomfilter completed
[+] Sorting data ... done! 8000000001 values were loaded and sorted
Base key: 35016f2fcc     
Base key: 6b02e0fb96     30 seconds: **100523485 keys/s**
Base key: 48044f7bb9     60 seconds: 100995345 keys/s
Base key: 5605bf57ab     90 seconds: 101805078 keys/s
Base key: f072b03f2       120 seconds: 101895372 keys/s
Base key: 790898c788      150 seconds: 102145283 keys/s

I think that the problem is related to the bloom filter multithread access and that will be solved in the version (Version 0.2.211018)

Metadata

Assignees

Labels

No labels
No labels

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions