Skip to content
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

table file is about 10m starting keys 0x1 #5

Closed
hamnaz opened this issue Feb 28, 2021 · 3 comments
Closed

table file is about 10m starting keys 0x1 #5

hamnaz opened this issue Feb 28, 2021 · 3 comments

Comments

@hamnaz
Copy link

hamnaz commented Feb 28, 2021

i just see your working code, its difrent from my invented 8 month old code , where i load in same ram 10x mean 100m keys and my logics, thats will work more 10 time faster then these codes, discus here or in discord group, ?

@albertobsd
Copy link

Yes a bigger bP table means more speed, theoretically the increment of the size of the bP table is lineal with the increment in the speed, but in practice sometimes this is not true at all, more points in memory means a bigger space in memory to access, more false positives in the Bloom filter or hashtable used, and in my case more binary searchs, depending of the size the increment in the speed can be only from 70% to 90% of the increment in bP table size

@hamnaz
Copy link
Author

hamnaz commented Feb 28, 2021

let me explain you, you compare full pubkey 66 in generated and minus to real pubkey for result , if you take first 12 char of pub in table, and compare, by this way same size of file, and same memory will work, just when compare hit first 12 char then generate full key for final compare, by this way you will pass 100m keys,m not 10m keys, tested these way before 8 months on cpu, yes if you build these on GPU, maybe much better

@iceland2k14
Copy link
Owner

Closing it as we discussed and already tested.

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

No branches or pull requests

3 participants