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

Tags not displayed for CPU, NVIDIA2, NVIDIA3. Same OC's applied across all GPU device groups. #455

Open
UserDC-LeGrand opened this issue Nov 19, 2022 · 3 comments
Assignees
Labels
enhancement New feature or request

Comments

@UserDC-LeGrand
Copy link

UserDC-LeGrand commented Nov 19, 2022

When using multiple device groups, Miner and Algo TAGs are not displayed on HiveOS dashboard for CPU and NVIDIA2 device groups, only for NVIDIA1.

image

image

@UserDC-LeGrand
Copy link
Author

Also noticed that OC's for NVIDIA1 get applied to NVIDIA2 and NVIDIA3 device groups as well, which can become a problem to manage, find a compromise OC between core and mem intesive Algo's, and resolve GPU stability issues.

@UserDC-LeGrand UserDC-LeGrand changed the title Tags not displayed for CPU and NVIDIA2 device groups Tags not displayed for CPU, NVIDIA2, NVIDIA3, and same OC's applied across all GPU device groups Nov 19, 2022
@UserDC-LeGrand UserDC-LeGrand changed the title Tags not displayed for CPU, NVIDIA2, NVIDIA3, and same OC's applied across all GPU device groups Tags not displayed for CPU, NVIDIA2, NVIDIA3. Same OC's applied across all GPU device groups. Nov 19, 2022
@MaynardMiner
Copy link
Owner

MaynardMiner commented Nov 21, 2022

If I remember correctly- The tags are sent at the same time oc is applied....And currently I have not created a way to read HiveOS oc sheets to determine oc for each gpu and apply them....So it's bound to group 1 (AMD1 or NVIDIA1).

This is something I really want to see added too, because I routinely divide up rig. It's just a large change/addition that I was witholding until I time I have the ability to just do a re-write where I can set up different threads to do different actions.

@MaynardMiner MaynardMiner self-assigned this Nov 21, 2022
@MaynardMiner MaynardMiner added the enhancement New feature or request label Nov 21, 2022
@UserDC-LeGrand
Copy link
Author

UserDC-LeGrand commented Nov 22, 2022

I now realize that this is not a simple one, and not even offered natively by HiveOS out of the box either... Prior to using SWARM, I dealt with the segration of GPU architecture, by laying them out in a common OC template, mapped to the Algo used by each miner/GPU grouping in my flightsheet. When I manually swtiched flightsheets, I needed to also switch the associated OC template... Not a simple thing to manage either manually, or "automatically" ... Only simple solution, is to not have mixed GPU architecture rigs, or have as many segregated rigs, as GPU architectures in your farm.

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

No branches or pull requests

2 participants