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.

Sign up for GitHub

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

Jump to bottom

using only 1 thread to mine even with 16 specified #5

Closed
n4kashu opened this issue Jan 26, 2019 · 0 comments
Closed

using only 1 thread to mine even with 16 specified #5

n4kashu opened this issue Jan 26, 2019 · 0 comments
Labels
bug Something isn't working

Comments

@n4kashu
Copy link

n4kashu commented Jan 26, 2019

Hey!

so when mining from daemon only ~10%CPU is utilized even when 16 threads are selected.
HR is around 4000h/s with any parameter passed to --threads .

behaves the same on win and linux..

reported by multiple users in telegram chat.

cheers!
@cryptozoidberg cryptozoidberg added the bug Something isn't working label Mar 9, 2019
wildkif pushed a commit that referenced this issue Mar 22, 2019
Wallet fixes #5 (4, 8, 12)
49a5edd
cryptozoidberg added a commit that referenced this issue Nov 12, 2019
@cryptozoidberg
exception safe destructor(CID 273246 (#5-1 of 5): Uncaught exception …
360c8bf 
…(UNCAUGHT_EXCEPT))
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@cryptozoidberg @n4kashu