Ethereum Wallet and 1080ti trouble
#1
Hello guys.
In another theme (https://hashcat.net/forum/thread-8000.html) i see, that a man has 14-20 h/s at the Scrypt (-m 15700) on 1080ti. But i try my 1080ti, and get only 1-2 h/s:
  • $ hashcat64.exe -m 15700 -b
  • hashcat (v5.1.0) starting in benchmark mode...

  • OpenCL Platform #1: NVIDIA Corporation
  • ======================================
  • * Device #1: GeForce GTX 1080 Ti, 2816/11264 MB allocatable, 28MCU
  • OpenCL Platform #2: Advanced Micro Devices, Inc.
  • ================================================
  • * Device #2: AMD FX(tm)-9370 Eight-Core Processor, skipped.

  • Benchmark relevant options:
  • ===========================
  • * --optimized-kernel-enable
  • Hashmode: 15700 - Ethereum Wallet, SCRYPT (Iterations: 1)
  • Speed.#1.........:        2 H/s (10199.56ms) @ Accel:1 Loops:1 Thr:1 Vec:1
On CPU i get 6 h/s. I try run bachmark on rig with 8 AMD RX580 and get 1 h/s from each card.
What's wrong? I have Win 10 and 442.19 Nvidia driver. i try 378.49 driver, but get same hashrate.
Also i have server with 2 x Xeon E5-2680v2 and Win 2019 server, but i can't install intel OpenCL runtime yet (it's installed, but not work. May be i should reboot the server). Without runtime on Xeon i get "Cannot find an OpenCL ICD loader library" message. After install runtime (v 18.1 x64) i get message "CL_PLATFORM_NOT_FOUND_KHR".
Reply
#2
It's called the cost factor (N, r, p parameters of scrypt).
your hash is probably: $ethereum$s*262144*1*8
their hash is: $ethereum$s*8192*8*1*

it's important to compare similar things, not apple and oranges. The cost factor changes a lot
Reply
#3
(02-15-2020, 12:15 PM)philsmd Wrote: It's called the cost factor (N, r, p parameters of scrypt).
your hash is probably: $ethereum$s*262144*1*8
their hash is: $ethereum$s*8192*8*1*

it's important to compare similar things, not apple and oranges. The cost factor changes a lot
I assumed that. But is it normally, that 1080ti have lower hashrate then AMD FX CPU?
Reply
#4
on scrypt that's not unexpected
Reply