@NotATether I want to see how many keys are generated when I run from the CPU and when I run from the GPU? I would like to see their difference on the speed of key generation?
In the interactive display it shows you the number of MKeys/s it is searching at for GPU and combined CPU/GPU use, like this:
Code:
$ ./VanitySearch -gpu 1notatether
VanitySearch v1.19
Difficulty: 10054102514374868992
Search: 1notatether [Compressed]
Start Mon Mar 1 06:53:26 2021
Base Key: 2A1422BAED92CCEAC4B23F7DF4CB207FAA88DC1D550D86EA3C6FE7D0881F08E5
Number of CPU thread: 1
GPU: GPU #0 GRID K520 (8x192 cores) Grid(64x128)
[123.15 Mkey/s][GPU 121.60 Mkey/s][Total 2^30.46][Prob 0.0%][50% in 1794.37y][Found 0]
VanitySearch v1.19
Difficulty: 10054102514374868992
Search: 1notatether [Compressed]
Start Mon Mar 1 06:53:26 2021
Base Key: 2A1422BAED92CCEAC4B23F7DF4CB207FAA88DC1D550D86EA3C6FE7D0881F08E5
Number of CPU thread: 1
GPU: GPU #0 GRID K520 (8x192 cores) Grid(64x128)
[123.15 Mkey/s][GPU 121.60 Mkey/s][Total 2^30.46][Prob 0.0%][50% in 1794.37y][Found 0]
The GPU speed is listed in the [GPU] bracket and the combined GPU+CPU speed is in the first bracket. There is no separate listing for CPU only.
(Yes, I mistakenly got a K520 so I'm stuck with compute cap 30 and CUDA Toolkit 10.2. I don't know the status of my other Tesla server yet. I guess on the flip side this makes it easier for me to run Bitcrack through a debugger even though it's non-reproducible there?
)@NotATether and another question, does it affect the key generation speed if I add a large list (70 million Bitcoin Addresses (P2SH) in uncompressed format)?
What do you mean? VanitySearch can't take a list of addresses, only a list of prefixes, and adding more of those will slow the program down.