I hereby claim:
- I am Chick3nman on github.
- I am chick3nman (https://keybase.io/chick3nman) on keybase.
- I have a public key whose fingerprint is 2038 8522 6798 6358 C9BE 8CD3 7AF8 194D 98A2 6A75
To claim this, I am signing this object:
I hereby claim:
To claim this, I am signing this object:
This benchmark was run on an Amazon EC2 p3.8xLarge instance with 4x Nvidia Tesla Volta V100 GPUs. | |
Nvidia Driver Version: 390.30 | |
Hashcat Release: 4.1.0 | |
hashcat (v4.1.0) starting in benchmark mode... | |
OpenCL Platform #1: NVIDIA Corporation |
Nvidia Driver version 411.63 | |
hashcat (v4.2.1) starting in benchmark mode... | |
OpenCL Platform #1: Intel(R) Corporation | |
======================================== | |
* Device #1: Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz, skipped. | |
OpenCL Platform #2: NVIDIA Corporation | |
====================================== |
hashcat (v4.2.1) starting in benchmark mode... | |
OpenCL Platform #1: Intel(R) Corporation | |
======================================== | |
* Device #1: Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz, skipped. | |
OpenCL Platform #2: NVIDIA Corporation | |
====================================== | |
* Device #2: GeForce RTX 2080, 2048/8192 MB allocatable, 46MCU |
Nvidia Driver Version: 419.35 | |
Fans were set to 100% for duration of the benchmark. | |
hashcat (v5.1.0-749-g5ecbcde9+) starting in benchmark mode... | |
OpenCL Platform #1: NVIDIA Corporation | |
====================================== | |
* Device #1: TITAN RTX, 6144/24576 MB allocatable, 72MCU |
This is a benchmark of the BETA CUDA branch of Hashcat, designed to run with both CUDA and OpenCL devices. | |
The Jetson Nano Dev Kit is an ARM SBC with a Jetson Nano (Maxwell 128 CUDA core) module attached. | |
Some modes failed due to the limitations of such a lower power GPU. | |
Access to the Jetson Nano was provided by Gridcoin(https://gridcoin.us/) Community member sodom89. | |
hashcat (v5.1.0-1029-g523e0f71) starting in benchmark mode... |
NVIDIA Driver Version: 441.66 CUDA Version: 10.2 | |
Fans were set to 100% for the duration of the benchmark. | |
hashcat (v6.0.0) starting in benchmark mode... | |
Benchmarking uses hand-optimized kernel code by default. | |
You can use it in your cracking session by setting the -O option. | |
Note: Using optimized kernel code limits the maximum supported password length. | |
To disable the optimized kernel code in benchmark mode, use the -w option. |
NVIDIA Driver Version: 455.23.05 CUDA Version: 11.1 | |
Credit: r4d1x | |
For benchmarking the card and allowing me to release the benchmarks here | |
There are a handful of algorithms failing, mostly appears related to SCRYPT and | |
is liking a tuning issue or small driver issue that we will need to take a look at. | |
Otherwise, seems fairly stable. | |
NVIDIA Driver Version: 456.38 CUDA Version: 11.1 | |
Credit: blazer | |
For benchmarking the card and allowing me to release the benchmarks here | |
There are some warnings about the CUDA Toolkit/Driver version but they dont appear to affect functionality or speed. | |
It appears to be some sort of version missmatch issue during detection and is seemingly just cosmetic. Noted for further investigation. | |
hashcat (v6.1.1-83-g90fb4aad) starting in benchmark mode... |
NVIDIA Driver Version: 450.80.02 CUDA Version: 11.0 | |
This is the PCIE variant of the Nvidia Tesla A100 GPU | |
The PCIE variant is limited to 250W and this limit is visible in the faster algorithms benchmarked | |
Clock speed is also limited on this card, which explains some of the numbers being lower than expected | |
When comparing to the RTX 3090, consider the difference in Power and Clock speed limitation, as well as the use of HBM2e memory instead of GDDR6x | |
A benchmark of the full SMX4 A100 variant will follow as I get access | |
hashcat (v6.1.1) starting in benchmark mode... |