hashcat Forum

Tesla P100 / HC 4.1.0 Benchmarks on Google Cloud:

Using some of my $300 in trial credit on Google Cloud / Hashcat 4.1.0

Results Attached.

Cool results, tnx!

Is there a way to distribute password cracking jobs across servers ?
(GC currently limits to a maximum of 4 Tesla P100's per account)

If so and your interested to try, signup for the free trial and let me know how to set this up!!

GC asked for a $140 deposit...
"To help us ensure that this is a legitimate request and that the resources you requested are available to you"

After you get the quota increase here are the basic steps I took to get this up and running:


sudo apt update
sudo apt upgrade

wget https://developer.download.nvidia.com/com..._amd64.deb

sudo dpkg -i cuda-repo-ubuntu1604_9.1.85-1_amd64.deb
sudo apt-key adv --fetch-keys https://developer.download.nvidia.com/com...a2af80.pub
sudo apt update
sudo apt install cuda

sudo reboot

nvidia-smi
sudo nvidia-smi --persistence-mode=ENABLED
sudo nvidia-smi --applications-clocks-permission=UNRESTRICTED

nvidia-smi -q -i 0 -d SUPPORTED_CLOCKS
sudo nvidia-smi --applications-clocks=XXXX,XXX (see output from SUPPORTED CLOCKS)

sudo apt install p7zip-full

wget https://hashcat.net/files/hashcat-4.1.0.7z
7z x hashcat-4.1.0.7z
./hashcat64.bin -b | tee hashcat-benchmark.txt

I'm curious how this would be setup and to see 8, 16, 32.... Tesla P100's running!

(04-13-2018, 08:00 AM)tebbens Wrote: [ -> ]Tesla P100 / HC 4.1.0 Benchmarks on Google Cloud:

Using some of my $300 in trial credit on Google Cloud / Hashcat 4.1.0

Results Attached.

I also tested the nvidia p100 on google cloud, can you confirm that with ethereum wallet -m 15700 the results are about: H/s 220?

With an Nvidia GT 1050 notebook I got about: H/s 1700. I can not understand...the P100 can not do better with Ethereum wallet -m 15700 than a 1050 ??!

I've been looking for days to recover my password ethereum *

Something doesn't seem right.... why am I only getting 13 H/s !?

Did I do something wrong ?

----

tebbens@hashcat:~/work/test$ ../hashcat-4.1.0/hashcat64.bin -b -m 15700 | tee hashcat-benchmark-ethereum.txt
hashcat (v4.1.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.

* Device #1: WARNING! Kernel exec timeout is not disabled.
             This may cause "CL_OUT_OF_RESOURCES" or related errors.
             To disable the timeout, see: https://hashcat.net/q/timeoutpatch
nvmlDeviceGetFanSpeed(): Not Supported

nvmlDeviceGetFanSpeed(): Not Supported

nvmlDeviceGetFanSpeed(): Not Supported

nvmlDeviceGetFanSpeed(): Not Supported

OpenCL Platform #1: NVIDIA Corporation
======================================
* Device #1: Tesla P100-PCIE-16GB, 4070/16280 MB allocatable, 56MCU
* Device #2: Tesla P100-PCIE-16GB, 4070/16280 MB allocatable, 56MCU
* Device #3: Tesla P100-PCIE-16GB, 4070/16280 MB allocatable, 56MCU
* Device #4: Tesla P100-PCIE-16GB, 4070/16280 MB allocatable, 56MCU

Benchmark relevant options:
===========================
* --optimized-kernel-enable

Hashmode: 15700 - Ethereum Wallet, SCRYPT (Iterations: 1)

Speed.Dev.#1.....:        3 H/s (12474.92ms) @ Accel:1 Loops:1 Thr:1 Vec:1
Speed.Dev.#2.....:        3 H/s (12484.49ms) @ Accel:1 Loops:1 Thr:1 Vec:1
Speed.Dev.#3.....:        3 H/s (12474.52ms) @ Accel:1 Loops:1 Thr:1 Vec:1
Speed.Dev.#4.....:        3 H/s (12485.34ms) @ Accel:1 Loops:1 Thr:1 Vec:1
Speed.Dev.#*.....:       13 H/s

Started: Tue May  8 04:56:43 2018
Stopped: Tue May  8 04:58:13 2018

In all the benchmark numbers you have posted, were you using the same hash or different hashes?