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

Application-locked slots #3229

Closed
smoe opened this issue Jul 19, 2019 · 2 comments
Closed

Application-locked slots #3229

smoe opened this issue Jul 19, 2019 · 2 comments

Comments

@smoe
Copy link
Contributor

smoe commented Jul 19, 2019

I run BOINC a former GPU mining rig - 6 GPUs with USB riser cards - that is mostly stable. It appears to be perfectly stable when mixing very I/O demanding projects with some that communicate less and/or that needs power. I would for instance very much like ot have one SETI job (non-demanding) always running, i.e. a slot dedicated to that project, combined with such from Einstein (needs more). If the designated project, SETI in my case, does not provide new WUs then that slot shall remain empty.

With BOINC I can somehow run different applications, but I can not assign resources to them so something gets always executed. For controling maximal power or maximal I/O, however, this would be really nice to have. Also, it somehow feels good to know that some pet project of yours is always active.

@smoe
Copy link
Contributor Author

smoe commented Jul 23, 2019

The Einstein@Home moderator, Gary, kindly pointed me to the max_concurrent feature in app_config.xml. That fixed it. I still think that this would be nice to see configurable also in the GUI. But I also see that this would open a whole new world of project-specific settings that the GUI (or the command line interface) are not addressing, yet.

@AenBleidd
Copy link
Member

@smoe, could this issue be closed now as far as you found a way to achieve what you want?
Project-specific changes is a whole new functionality that is much more complex and should be reviewed and discussed separately.

@smoe smoe closed this as completed Jul 27, 2019
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

2 participants