The use cases I have heard of which would benefit such a feature is
(say) for database threads which want to change their "resource
affinity" status depending on which customer query they are currently handling. If they are handling a query for a "important" customer, they will want affinied
to a high bandwidth resource container and later if they start handling
a less important query they will want to give up this affinity and
instead move to a low-bandwidth container.
hmm, would it not be better to have a thread each in two different
containers for handling different kind of requests.
Or if there is too-
much of sharing between threads, then setting the individual priority
should help.