albertobsd/keyhunt

Real Speed

Opened this issue · 10 comments

Anyone care to answer what is the real speed with bsgs mode ?
I mean how many UNIQUE keys per seconds are checked, not including the "compared" ones inside the bloom files.
Here is a .gif showing low settings on -k and I clearly seen a few keys (2-3 ) / second even it's showing 590 terrakeys/sec.
Usually on so high speeds I shouldn't see clear keys on terminal.
Alberto, how to check the real speed ? For example if I have 10 exa/s , how many UNIQUE keys are checked per second ?
Recording 2024-11-14 185612

dem10 commented

You are not looking at the screen carefully. The random initial key changes and then N keys are checked sequentially and this is a cycle. Pay attention to the parameter N = 0x10.................If you want to calculate the real speed, you should have carefully read ReadMe https://github.com/albertobsd/keyhunt?tab=readme-ov-file#is-my-speed-real If I remember correctly endomorphism does not work in BSGS mode and enable silent kernel mode it will increase speed if you don't like looking at pretty numbers.

I understand that the search is sequential based on N number, starting from the end of the range but I want to know how many unique keys are generated without sequential. I don't know how to explain and english is not my native language.
-q doesn't help me at all, the same speed if it's silent or not.
Recording 2024-11-14 193338

dem10 commented

You didn't understand anything. After each N consecutively checked keys, the starting random key changes and everything repeats - it's a cycle. All you see is a change in the starting random key.Turn on the -q command and the speed will increase even more.

That's what I'm asking, how many unique keys are checked AFTER finish cheking N sequential keys, thanks for you time anyway
edit: i'm interested in the number of starting random key per second , excluding sequential search.

dem10 commented

All you see is a random key selected from the range. Next, look at the parameter N = 0x1000....., these are sequential keys from the random key in hexadecimal format, which the tool will check and start the cycle again.

a simple question: how many cycles per second? :) I'm not interested what's happening inside each cycle, sequential etc, how many cycles per second ? How is this calculated and reflected in the shown speed ?

dem10 commented

It all depends on the frequency of your processor and RAM. Your first screenshot shows the change of the random key. All other operations in BSGS are not shown.

Those screenshots are from a desktop computer just for testing. I have a server with keyhunt running on it.
Screenshot 2024-11-14 202623
Screenshot 2024-11-14 202723

a simple question: how many cycles per second? :) I'm not interested what's happening inside each cycle, sequential etc, how many cycles per second ? How is this calculated and reflected in the shown speed ?

The -t parameter determines how many threads will be started. The check will come from each thread + value -n. The value n determines the number of cycles per second (if there are several cycles per second, the value n will be small)

Wish there was a clear formula to check the real number of random keys checked per second, excluding those "compared" with the bloom files or sequential search. Maybe I don't understand how the bloom filter is working but for sure that speed showed on terminal is not the real one.