So far I've only been able to tune the database for performance. Which is great because it's critical.
Currently no way of optimizing Apache. Like if we find and update Apache conf file it will get wiped during next updates, so we're limited by whatever defaults are running.
The UI allows for customizing php-fpm and also customizing ModSecurity conf. I think that's all we get for now.
Enhance is pretty much unusable for me until I can verify and customize Apache conf, so really hoping that gets rolled out soon. I thought it was in the roadmap, but not seeing it anymore, maybe I just read one of the devs mention it... One config for Apache can't work, what if max workers is set to like 500 on a server that's capable of maxing out 20,000? Then that server is just a waste - or the app will be crippled for performance due to poor config.
I've read some ppl finding and customizing Apache conf file regardless of the fact it gets wiped during updates, but that's not acceptable for a production server. We need conf file access + persistence.