Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Benchmark off by 10x #545

Closed
TheDailySpank opened this issue Feb 7, 2019 · 2 comments
Closed

Benchmark off by 10x #545

TheDailySpank opened this issue Feb 7, 2019 · 2 comments

Comments

@TheDailySpank
Copy link

  • Your current Server version located at the bottom of any Hashtopolis webpage: 0.10.1
  • Current Client version: Latest
  • Your current Hashcat version: 5.0.0
  • The exact task command you are trying to run: mask attack on SHA1 wordlist

Currently testing on three different setups before rolling out to 72 GPU mining rig and I've run into an issue where one of the CPU client's benchmark is off by 10x. The other dual GPU and single CPU clients works as expected and typically show ~1-2% progress each update and take roughly the 600 seconds to finish a chunk. The bad machine does about 10-20% progress each update and finishes a chunk in about 10-15 seconds.

The improperly performing CPU instance will behave as expected if I manually assign the GPU's benchmark to it (around 40Mh/s give or take).

I have tried both benchmark options and all clients perform the same (2 good, 1 bad).

I'm worried that when it gets rolled out to the bigger rig, I'll end up having clients spend more time reading and re-reading the hashlist than actually doing real work, especially if it ends up doing something like being 100x off the mark.

@TheDailySpank TheDailySpank changed the title Benchmark off by 10xx Benchmark off by 10x Feb 7, 2019
@0xVavaldi
Copy link
Contributor

#551 might be relevant to this.

@zyronix
Copy link
Member

zyronix commented Jun 16, 2023

Closing old issue. If this is still an issue please reopen new one.

@zyronix zyronix closed this as not planned Won't fix, can't repro, duplicate, stale Jun 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants