I tested bsgsd sever and it also is pretty fast
Nice, not much people test it because not much knows that the server exists
I know printing to screen will cause lost of speed but, is there any way I can check exactly how many keys/s are running in bsgsd?
To keep the best performance in the server i should recommend not to look for this on the server side.
Instead of it i should recommend to this on client side, in the BSGSD.md file i post a small python client, since performance is not required on client python fit perfectly for this situation, you can send small chunks of work to the server something like 50 to 55 bits of subrange and edit the client output to print the speed:
# Loop for sending and receiving messages
for i in range(num_iterations):
reply, elapsed_time = send_and_receive_line(host, port, message)
if reply is not None:
# speed = subrange / elapsed_time
print(f'Received reply: {reply}')
print(f'Elapsed time: {elapsed_time} seconds')
# print(f'Speed: {speed} keys / seconds')
In that code you need to set the sub-range value, this require to know what are you doing but you can get more or less the speed that you are getting in each time.
I hope this workaround fit your needs because to be honest i don't see any necessary to print the speed on the server side, it was made to attend clients without the need to be in front the same terminal.
Will be any speed improvement in the future for bsgsd or bsgs key generator?
For CPU i doubt it, I already did a lot of improvements compared against the BSGS of JLP i think that i realdy reach the CPU speed limit.
The only possible improvement will be implement another faster storage for the Baby table and bloom filters or the use of GPU (It need to rewrite all the code)
albert0bsd, thanks for all your work!!!
Thanks, you're more than welcome.
Regards!
