Andi Kleen notes that:
| Tunables are basically "we give up, let's push the problem to the user"
| which is not nice. I suspect a lot of users won't even know if their
| workloads are bursty or not. Or they might have workloads which are
| both bursty and not bursty.
Tunables are also something for external daemons to change: the famous
example is the IBM z/OS Workload Manager (WLM), which looks at
application (actually workload) progress and a table of requirements
and adjusts CPU, IO and memory tunables to speed to slow the workload.