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

Excavator not closed after benchmark finished #14

Closed
rinkal26783 opened this issue Aug 12, 2018 · 2 comments
Closed

Excavator not closed after benchmark finished #14

rinkal26783 opened this issue Aug 12, 2018 · 2 comments
Assignees
Labels
answered question Further information is requested

Comments

@rinkal26783
Copy link

image

@RainbowMiner
Copy link
Owner

Excavator is handled different: it is controlled through a build-in API by RainbowMiner. To avoid multiple Excavator windows and reduce switching times, Excavator will always stay open. The next time, an algorithm needs to be mined through Excavator, RainbowMiner controls and reactivates the already opened Excavator (without the need to reopen it again). Also, if your rig contains multiple different GPU, the one Excavator could handle all selected algorithm at once.

RBM

@RainbowMiner
Copy link
Owner

Just minimize it and forget about it :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
answered question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants