New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Comments
How exactly do you measure that?
Site24x7 alert
killall php-fpmAnd hand in the resignation thereafter
Did you enable opcache?
I have it enabled
Which PHP version are you currently using? If your apps are compatible with 8.3, then it's advisable to upgrade for better performance and reduced load.
what are you doing with your other hand with a profile pic like that?
Off topic
you were doing something off tropical ?
What are your settings for php-fpm? When do you see the CPU usage on 100%? Does it happen randomly or does it happen when there's a traffic spike? Did you enable slow log?
As @amit177 suggested, the PHP slow log is a great place to start. This will identify any scripts that are running for longer than some threshold you set. Poorly written scripts can be a cause of high CPU utilization, so that's a key way to find out where your problems are.
Start with a higher value like 5 or 10 seconds to see if you have any really long-running scripts. Then gradually reduce the number until you've identified all of the troublesome ones. From there, you can work backwards to find the specific functions that are taking so long to execute.
First, find an exact website that makes 100% load; you can do that with a status page, for example. Next tail -f access.log of that website. If there are a lot of requests per second - it's DDoS or some kind of parser or visitor's peak. If requests are rare - isolate slow requests and try to debug it with google / reading code / strace ...
have you tested using profiler like xdebug?
maybe create a dev environment first then use xdebug to identify bottlenecks on your php app?