Resolved The new function Dedicated FPM application served by Apache

[ghazestor]

We've turned this on for higher tier customers and definitely significant boost in speed as they're not waiting for free workers but its also jacked up short term average CPU utilisation by 20-30% because more peak CPU is available to be used.

 

[Hangover2]

@ghazestor We did not experience any increased CPU total usage. Based on your settings the free workers are not the ones to blame. The speed increase comes from the dedicated master processes per website having their own OPcache. This can improve PHP performance dramatically by storing precompiled script bytecode in shared memory for the PHP handler. This removes the need for PHP to load and parse scripts on each request. This normally even brings CPU usage down. Of course you pay a price for that: the memory usage increases based on the settings for [opcache] in the php.ini. The shared FPM application handler on the other side never has really a chance to cache PHP scripts very long as the different websites kick each other out of the cache again and again - at least with the standard [opcache] settings in Plesk. Furthermore the PHP function opcache_get_status has to be disabled for obvious security reasons.