This message was deleted.

burn it all down

• CPU clamping is a brute force approach that is computationally expensive. To keep the CPU usage of a troublesome process artificially low, it is better to use CPU spike protection, at the same time as assigning static CPU priorities and CPU affinities to such processes. CPU clamping is best reserved for controlling processes that are notoriously bad at resource management, but that cannot stand to be dropped in priority. https://docs.citrix.com/en-us/workspace-environment-management/service/using-environment-management/system-optimization/cpu-management#cpu-clamping

Yea, don't do that for teams. I used clamping on crazy run away processes like legacy adobe parts that's need for a print Que but then gets stuck and supposed to end after its called which then runs like a wild stallion destroying CPU cycles. I have been testing the new teams and I believe it will be the Saving grace in time for CVAD.

Thanks for the feedback guys....i was stuck in a P1 on Friday and was looking for any CPU i could claw back from processes