Which GPU to buy to search BISS keys in TABLE V1

campag5242

Feed Hunter
Messages
2,585
Thanks, I came across such discussions already.

Rough and ready comparison: Ubuntu's Disks/Benchmark is giving similar (but slower) timings to that which W10 Task Manager/Performance shows during a live search. Currently I'm adding more timing stats to aid understanding. Average for 65k disk searches on little arm box: 36us, on W10: 492us
 

campag5242

Feed Hunter
Messages
2,585
:oops:
Refactoring so that the three steps of RBT search were done serially (so calc all end6 -> disk search all -> rebuild all chains), not in parallel rounds of smaller slices, I see that the disk search is indeed *slower* on the Jetson (as it should be). My timings info gathered when doing all in parallel was in error. Sorry!
 

campag5242

Feed Hunter
Messages
2,585
I followed some of the tips here: https://windowsreport.com/fix-slow-ssd-windows-10/
Flicking a switch on my PCI-E SATA board to enable AHCI got the search down to 425usec from 492 on a 400GB table.
Installing the same Crucial 1050GB SATA3 on another PC with spare motherboard SATA ports, and this became 330usec, for a 400GB table *disk search* in 22.1sec.
I'm curious how fast M.2 might be, but not so curious to spend EUR200 to find out :)
 

C0der

Senior Member
Messages
270
Harddisk only search time on a 53GB V1:
SATA: 160 sec.
M.2: 143 sec.
(low price M.2 tho)
 

campag5242

Feed Hunter
Messages
2,585
Thanks C0der - good to know, and I'm sure glad I'm a skinflint since making sure my hardware was configured properly (eg using AHCI mode on PCI-e SATA adapter sure beats using USB 3.0 adapter etc) alone has it working much faster than before for a FREE boost in performance.
 

orangebirds

Senior Member
Messages
399
Any recomendations for a videocard < 500 Euro?
How long does it take to find keys?
In my case, I got GT740 that I bought many years ago.
for v1, it took me 10 minutes max before search fail with 318GB official table on SATA SSD with disk search taking 6 minutes

but, new, more powerful cards and M.2 SSD should get you going way better than that
 

moonbase

VIP
Donating Member
Messages
583
Any recomendations for a videocard < 500 Euro?
How long does it take to find keys?


Any old cheap used NVIDIA card will be OK for searching tables.
The speed differences between a cheap 10 year old card and a modern card for searching are not huge in terms of minutes.

Older cards such as GT710 or GT730 will be OK.
An SSD or m2. nvme drive will provide faster searching of tables compared to an HDD, this is possibly the area to get decent spec?

For creating v1 chains and tables you need the best NVIDIA GPU that you can afford. In this instance better cards offer huge speed gains.
 

scannie

Registered
Messages
12
I see I don't have enough knowledge to understand above.
I don't know the difference between searching and creating tables.
Information is hard to find.
Without this information I stop this project.
 

dvlajkovic

Senior Member
Messages
499
If you want to watch the sat-feeds enc in biss, you will search the pre-calculated tables to find the cw.
You'll need an ordinary nvidia GPU to do it.
The bigger the pre-calc tables you've got, the merrier the chance to find the cw.

This leads you to the 2nd part of the story: how to increase the size of your pre-calculated tables?
For this you'll need a much faster nvidia GPU than the one used just for searching.
 

C0der

Senior Member
Messages
270
Estimation:
Creating a new table with 50% success rate will take about 2 month on a GTX1050.
Maybe 2 days on a 4090.
 

moonbase

VIP
Donating Member
Messages
583
That means creating pre-calculated tables takes a lot of time?
Is there an overview? Which card, how many times does it take?


There are online downloads of pre-built tables.
If you download pre-built tables you do not have to create them

Search this forum for past posts on the topic of csa rainbow tables, there were a lot of useful posts made on this subject.
 

moonbase

VIP
Donating Member
Messages
583
Estimation:
Creating a new table with 50% success rate will take about 2 month on a GTX1050.
Maybe 2 days on a 4090.


I have not yet tested the v1 chain creation speed with a 4090.
It's an easy quick test, might give it a go later.

What size v1 table in terms of chains would you estimate for 50% success rate please?
I think Colibri said originally that a 256 chain v1 table might be good for 90%. However, I am not certain on that point.
 

moonbase

VIP
Donating Member
Messages
583
43 GB for 50%
223 GB for 90% in one table
160 GB for 90% in two tables


A quick check using an RTX 4090 GPU in an X99 board with i7-5930k CPU creates one chain in 32 minutes.
The daily rate from this is 45 chains per day.

One Table (50%):
43GB is approximately 56 chains based on the default chain size of 786432KB per chain.
This size table would take just under one and a quarter days to create 56 chains for a 50% hit rate in one table.

One Table (90%):
223GB is approximately 290 chains based on the default chain size of 786432KB per chain.
This size table would take just under six and a half days to create 290 chains for a 90% hit rate in one table.

Two Tables (90%):
160GB is approximately 209 chains based on the default chain size of 786432KB per chain.
This size table would take just over four and a half days to create 209 chains for a 90% hit rate using two tables.


The speed figures above can probably be increased by using a 12th or 13th generation board and CPU which can fully utilise the PCIe 4.0 status of an RTX 4090.
The X99 platform is PCIe 3.0 which might be bottlenecking the RTX 4090 GPU.
 

C0der

Senior Member
Messages
270
At some point (around 86%) we get a better success rate by creating two seperate tables.
Its a little change in the code.
Colibris tools dont have that option.

(The one table setting is a bit faster in finding the CW tho.)
 
Top