Well, In my opinion configurable autotuning exists. Do not confuse a server that never reboots, with a system that never stops. For example the AWS services in

Well, In my opinion configurable autotuning exists. Do not confuse a server that never reboots, with a system that never stops. For example the AWS services integrate metrics to define behaviors (scale up, scale down, etc), you can implement pretty convenient autotuning algorithms, even those that learn from previous metrics. The Linux kernel networking and I/O layers are plenty of autotuning code. Powertop is just another example maybe. Even a perl interpreter makes some dark magic. If I think on my own systems implementation, I think I have do noob autotuning too (alert control, alert frequency, recovery steps, recovery notification... systems increasing their swap before a cron runs, dynamic filtering tables based on app/network input, sysctl autotuning daemons.... etc...) There are too much to improve regarding autonomous systems, but autotuning is just about programing programmable components, for react on events. Depending on those components, you have to coordinate some kind of events or very different ones. From IRQ interrupts, to a cache hit in the other end of the connection, there are a plenty of parts to implement autotuning, from many vendors, and maybe, this is the root of the issue.