3) resctl just uses COS under the hood. The same limitation applies > Yeah, that gives you 9ish usable slices which is not very much. Again that was my point

3) resctl just uses COS under the hood. The same limitation applies > Yeah, that gives you 9ish usable slices which is not very much. Again that was my point This is 9 ways that you can use for your latency-sensitive workloads exclusively. This is MUCH better than letting all that LLC get trashed by non-critical processes/threads. Typically after applying such partitioning we've observed a 15-20% speed up in our apps. In my area shaving off a few micros that way is a huge deal and definitely worth spending a couple of minutes implementing.