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

Feature Request: MiningRigRentals add an option set a Rig as only GPU or only CPU? #330

Closed
paulpoco opened this issue Nov 22, 2018 · 4 comments
Assignees
Labels
enhancement New feature or request implemented an enhancement has been implemented pool issue

Comments

@paulpoco
Copy link

Feature Request: MiningRigRentals add an option set a Rig as only GPU or only CPU?

Right now if I setup a Rig for YescryptR32 and I want it to be CPU, I don't think Rainbowminer will know which device is to be used. You set your hash rate to rent on the website, if I set for the hash for CPU I don't want Rainbowminer to start using the GPU with a much higher hash rate than the CPU, this would give the Renter tons of extra hash for the cost of a lower CPU hash.

So maybe on MRR Rig Description, where you have [rainbowminer] add the option to have [rainbowminer,CPU] or [rainbowminer,GPU]?

@RainbowMiner
Copy link
Owner

Good point. For the moment, I would put the YesCryptR32 onto the list "ExcludeAlgorithm" for the GPUs in devices.config.txt . I will figure out some better option, in the meantime.

@paulpoco
Copy link
Author

paulpoco commented Nov 23, 2018

YesCryptR32

I tried that. You cannot have 2 different rigs at the same time. When I make it active, within a few minutes it get disabled.

Currently have X16R running.

@RainbowMiner
Copy link
Owner

RainbowMiner commented Nov 23, 2018

I tried that. You cannot have 2 different rigs at the same time. When I make it active, within a few minutes it get disabled.

I will check that. In the current version, the MiningRigRentals pool module is restricted to one instance per rig (because it scans for the rig's worker name). My plan is to extend this on a per model name base (e.g. CPU, GTX2070..). This is kind of difficult, but I already have an idea on that.

@RainbowMiner RainbowMiner added enhancement New feature or request implemented an enhancement has been implemented labels May 23, 2019
@RainbowMiner
Copy link
Owner

This is already implemented, by now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request implemented an enhancement has been implemented pool issue
Projects
None yet
Development

No branches or pull requests

2 participants