-
Notifications
You must be signed in to change notification settings - Fork 110
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
[VOTE] Miner groups #302
Comments
That sounds like a very useful thing. Currently i don't have a good idea howto integrate that. I can't find anything useful about that with the datatable the dashboard is using. A simple approach could be to prefix the miner names with for example low_ or high_. Then you could sort by name. And then you don't have to select them one by one, you can select them all in a row by selecting the first element + keep pressing the I'm still looking into something better |
Another approach could be that we add another field to the miner. For example |
If i understand correctly you don't know a way to just add another button 'Select group' (in addition to 'Add to group' and 'Remove group') with dropdown that just selects all miners in it by one action ? Didn't know that you can select first miner in list and then select last one with shift if you want to select them in bulk, that simplifies things a bit but the main usecase of groups would be say, i have several miners that don't work good with Rx algos, it doesn't really depends on LLC amount, more on RAM but since it isn't reported in dashboard (yet) there's no way to filter miners, just to remember which ones not to assign Rx algos, adding them in group would help a lot. Workaround with prefixing the miner name would do for now, didn't think about that, thing is i don't have 10 miners, i have ~120 of them so renaming them one by one would be very tedious. |
I think group in name/workerid would be a good idea... and in front group in table like algo? (or subgroup) GROUP.NAME how to vote? x) |
Manual grouping of miners.
I.e, say i have 10 miners, 3 of them are have low amount of LLC which don't work with Rx algos very well, so i add them to group 'low-LLC' and other miners to group 'high-LLC', then to easy push config changes to either of them i just select entire group instead of sorting entire list by LLC amount and selecting them one by one.
The text was updated successfully, but these errors were encountered: