• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Slow requests and poor availability

AFRC

New Pleskian
Hi,

I'm experiencing some issues regarding connectivity.
I have new relic for monitoring and i'm getting poor results on some pings.

Globally the server performs well. It has only one site and the app performance is good.

I think these slow requests are on the connectivity and usually happen late in night (~3am).
During the day when the server has the highest load we rarely experience this.

relic.png

Usually these requests take 600 to 900ms.
Backups are scheduled to 5am, so it is not related.

Thanks.
 
I have come to realise that MySQL has away of increasing ping response times on a server ...
This also be a result of slow queries, huge tables and lots more ...Normally I use mytop to monitor the MySQL queries and activities to give me an indea of what could be causing the same ..Give it a try, you might get an idea of the cause.
 
Thanks for your feedback.
We currently dont have any issues with mysql. No slow queries. Database is performing really well: under 40ms
 
It seems some it's some kind of routine that trigger services to restart.
We have pingers running every minute and sometimes the pingers catch these small downtimes. At least it's my suspicion

Is there any way to trace this?

Thanks.
 
Back
Top