December 6, 20196 yr Searched and Googled this but have been reliably told this isn't currently available. Description Allow resources (VMs or Dockers) to isolate CPUs to themselves only when they are running: If the resource is running: Only it can use it's designated cores If the resource is not running: Anything can use them Use Cases/Scenarios You have a VM that is is only used when a user is present, especially interactive VMs (desktops and gaming) which you only use when you are awake. When it's not in use, it may as well be shut down and the resources released, for example, overnight. You have a Docker that can be resource hungry, but isn't interactive and could be run during scheduled times. Backups or F@H would be a good example if you only back up nightly. You're out, and neither of the above two scenarios are occuring and you're out of the house watching Plex remotely. It might as well have all the server resources avaialble in case you have more streams than normal.
December 13, 20196 yr I don't think the feature, as you described it, will ever be implemented by Unraid. It sounds simple in your head but is an extremely complicated change. On-demand CPU core isolation needs to be implemented by Linux at the kernel level e.g. creating a communication mechanism to lock and release core isolation (that is assuming core isolation is something that can be done after boot). On-demand core usage change for dockers needs to be implemented by Dockers. (remember, currently if you pin an isolated core to a docker, it will cripple the docker) IFTTT condition + GUI implemented by Limetech (1) and (2) are not controlled by LT (nor it is within LT capabilities, to be honest). So unless and until they are implemented by those entities, nobody (LT included) will be able to implement what you are asking.
Archived
This topic is now archived and is closed to further replies.