Skip to content
This repository has been archived by the owner on Jul 29, 2018. It is now read-only.

Multi-GPU broken #18

Closed
Lignum opened this issue Jan 12, 2016 · 7 comments
Closed

Multi-GPU broken #18

Lignum opened this issue Jan 12, 2016 · 7 comments
Assignees
Labels

Comments

@Lignum
Copy link
Collaborator

Lignum commented Jan 12, 2016

I'm running the miner with -a, however it only mines on a single GPU. -l finds two GPUs, same signature, of course, but differing IDs (0 and 1).

@Lignum Lignum added the bug label Jan 12, 2016
@dmarcuse
Copy link
Owner

I think I know why this is happening - I'll work on a fix.

@dmarcuse dmarcuse self-assigned this Jan 12, 2016
@dmarcuse
Copy link
Owner

Should be fixed in latest beta code as of 8954f6c.

@Lignum
Copy link
Collaborator Author

Lignum commented Jan 13, 2016

Indeed. Cheers!
However, I seem to get unusually low hash rates... being around 70MH/s. Considering that my GPU screams around that rate, which it does, it's not just a miscalculation. I'm running 8954f6c, for reference.

EDIT: Also happens on 72ff834.
EDIT 2: Mining on a single GPU halves the hash rate to 35MH/s... this might be obvious to point out, but just making sure you know enough.

@dmarcuse
Copy link
Owner

72ff834 isn't any different from 8954f6c as far as the Java side is concerned.

Can you try running the profiler again and using the arguments it gives you?

@Lignum
Copy link
Collaborator Author

Lignum commented Jan 13, 2016

Sure thing. The profiler gave me -d 1912350326:4194304, which doesn't fix the issue. It may be worth pointing out that the profiler can reach 160MH/s perfectly fine.

@Lignum
Copy link
Collaborator Author

Lignum commented Jan 13, 2016

To further narrow it down, c7b3333 can do the job perfectly fine aside from the then-existing Multi GPU issue.. so it must've been a change in 8954f6c.

@dmarcuse
Copy link
Owner

Fixed as of 43deb8e.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants