Nvidia 3080 Ti Benchmark
#1
The 3080 Ti is very close to the 3090 
Code:
OpenCL API (OpenCL 3.0 CUDA 11.3.121) - Platform #1 [NVIDIA Corporation]
========================================================================
* Device #1: NVIDIA GeForce RTX 3080 Ti, 11328/12288 MB (3072 MB allocatable), 80MCU

Benchmark relevant options:
===========================
* --optimized-kernel-enable
* --workload-profile=4

Hashmode: 0 - MD5

Speed.#1.........: 66673.1 MH/s (39.82ms) @ Accel:32 Loops:1024 Thr:1024 Vec:8

Hashmode: 100 - SHA1

Speed.#1.........: 21269.1 MH/s (125.70ms) @ Accel:32 Loops:1024 Thr:1024 Vec:1

Hashmode: 1400 - SHA2-256

Speed.#1.........:  9046.4 MH/s (296.23ms) @ Accel:32 Loops:1024 Thr:1024 Vec:1

Hashmode: 1700 - SHA2-512

Speed.#1.........:  2682.5 MH/s (249.68ms) @ Accel:16 Loops:512 Thr:1024 Vec:1

Hashmode: 22000 - WPA-PBKDF2-PMKID+EAPOL (Iterations: 4095)

Speed.#1.........:  1048.9 kH/s (311.48ms) @ Accel:32 Loops:512 Thr:1024 Vec:1

Hashmode: 1000 - NTLM

Speed.#1.........:  118.5 GH/s (22.25ms) @ Accel:32 Loops:1024 Thr:1024 Vec:8

Hashmode: 3000 - LM

Speed.#1.........: 63251.8 MH/s (41.85ms) @ Accel:512 Loops:1024 Thr:64 Vec:1

Hashmode: 5500 - NetNTLMv1 / NetNTLMv1+ESS

Speed.#1.........: 63103.2 MH/s (42.09ms) @ Accel:32 Loops:1024 Thr:1024 Vec:2

Hashmode: 5600 - NetNTLMv2

Speed.#1.........:  4663.5 MH/s (287.29ms) @ Accel:16 Loops:1024 Thr:1024 Vec:1

Hashmode: 1500 - descrypt, DES (Unix), Traditional DES

Speed.#1.........:  2588.0 MH/s (258.55ms) @ Accel:128 Loops:1024 Thr:64 Vec:1

Hashmode: 500 - md5crypt, MD5 (Unix), Cisco-IOS $1$ (MD5) (Iterations: 1000)

Speed.#1.........: 28777.8 kH/s (87.70ms) @ Accel:32 Loops:1000 Thr:1024 Vec:1

Hashmode: 3200 - bcrypt $2*$, Blowfish (Unix) (Iterations: 32)

Speed.#1.........:    94241 H/s (145.19ms) @ Accel:16 Loops:32 Thr:11 Vec:1

Hashmode: 1800 - sha512crypt $6$, SHA512 (Unix) (Iterations: 5000)

Speed.#1.........:  453.6 kH/s (286.76ms) @ Accel:16 Loops:512 Thr:1024 Vec:1

Hashmode: 7500 - Kerberos 5, etype 23, AS-REQ Pre-Auth

Speed.#1.........:  1424.0 MH/s (470.78ms) @ Accel:512 Loops:256 Thr:64 Vec:1

Hashmode: 13100 - Kerberos 5, etype 23, TGS-REP

Speed.#1.........:  1409.0 MH/s (475.79ms) @ Accel:256 Loops:512 Thr:64 Vec:1

Hashmode: 15300 - DPAPI masterkey file v1 (Iterations: 23999)

Speed.#1.........:  177.1 kH/s (315.18ms) @ Accel:16 Loops:1024 Thr:1024 Vec:1

Hashmode: 15900 - DPAPI masterkey file v2 (Iterations: 12899)

Speed.#1.........:  101.6 kH/s (255.30ms) @ Accel:8 Loops:512 Thr:1024 Vec:1

Hashmode: 7100 - macOS v10.8+ (PBKDF2-SHA512) (Iterations: 1023)

Speed.#1.........:  1267.1 kH/s (255.93ms) @ Accel:4 Loops:1023 Thr:1024 Vec:1

Hashmode: 11600 - 7-Zip (Iterations: 16384)

Speed.#1.........:  1003.1 kH/s (300.80ms) @ Accel:16 Loops:4096 Thr:1024 Vec:1

Hashmode: 12500 - RAR3-hp (Iterations: 262144)

Speed.#1.........:  137.8 kH/s (296.85ms) @ Accel:64 Loops:16384 Thr:128 Vec:1

Hashmode: 13000 - RAR5 (Iterations: 32799)

Speed.#1.........:  112.7 kH/s (362.47ms) @ Accel:16 Loops:1024 Thr:1024 Vec:1

Hashmode: 6211 - TrueCrypt RIPEMD160 + XTS 512 bit (Iterations: 1999)

Speed.#1.........:  783.7 kH/s (383.73ms) @ Accel:8 Loops:1024 Thr:1024 Vec:1

Hashmode: 13400 - KeePass 1 (AES/Twofish) and KeePass 2 (AES) (Iterations: 24569)

Speed.#1.........:  137.2 kH/s (397.71ms) @ Accel:16 Loops:1024 Thr:1024 Vec:1

Hashmode: 6800 - LastPass + LastPass sniffed (Iterations: 499)

Speed.#1.........:  7299.2 kH/s (351.09ms) @ Accel:32 Loops:499 Thr:1024 Vec:1

Hashmode: 11300 - Bitcoin/Litecoin wallet.dat (Iterations: 200459)

Speed.#1.........:    13635 H/s (490.43ms) @ Accel:16 Loops:1024 Thr:1024 Vec:1
Reply
#2
Can you post --benchmark-all
Reply
#3
Can you also confirm if you're using an Limited Hash Rate RTX 3080Ti? I've not seen how this will impact hashcat.
Reply
#4
(06-09-2021, 11:37 PM)squidman Wrote: Can you also confirm if you're using an Limited Hash Rate RTX 3080Ti? I've not seen how this will impact hashcat.

https://twitter.com/Chick3nman512/status...2005943299
Reply
#5
I'm sorry but I saw that tweet and would still ask question about LHR and more details about the tests to verify.

If I remember correctly NVIDIA said that the limit take effect after they see a specific memory usage for some time and if that pattern is gone (for some time) they will lift the limit again. Thus I would not suspect any penalty by running hashcat benchmarks even if they are effected, too.
Well but NVIDIA also said for 3060 that the limiter will only be there for etherium mining and that it is not only the driver but a combination of driver and firmware which will make it unbreakable -- and then they break it with their own beta driver for developers.
With all this in mind (and that often people think that the limiter is there all the time) it would be nice to know how it was tested that these cards are not affected and what other tests are planed. To be honest I am not sure how I would test that, because maybe only 3 or maybe only 23 or maybe 53 algorithm of hashcat are affected and the rest is not. Maybe this was all planed and considered by the test already done, that would be awesome; it would be nice to know.

But the limit is not the only thing NVIDIA did to prevent hobby mining etherium (the big companies would use their own driver and firmware anyway). They limit the number of cards that could be used for full speed to mostly one card and they did not break that with their driver. Well but the miner could get around that to use up to 7 cards in one rig (which seems to be the normal number, I guess).
Are there any tests with multiple cards an hashcat? Up to now I only saw one card used.

Oh and because there was a question about if the above card is a LHR card or not: All 3080 TI and 3070 TI on the market should be LHR card -- all 3060, too, if you ignore the driver flop. For 3060 TI, 3070 and 3080 there should be both options LHR and non-LHR cards and it seems that NVIDIA force their vendors to mark the LHR cards as LHR in any way.
So to speak, the above card should be LHR because there are only LHR cards of 3080 TI, only the pre release test cards where partly non-LHR (and these chips should have other ids, meaning you cannot use the test driver for the market gpus).
Reply
#6
Hashcat performs excellent on multiple GPU. Is tested very often.
Reply