• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • Our UX team believes in the in the power of direct feedback and would like to invite you to participate in interviews, tests, and surveys.
    To stay in the loop and never miss an opportunity to share your thoughts, please subscribe to our UX research program. If you were previously part of the Plesk UX research program, please re-subscribe to continue receiving our invitations.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

Issue Slow mySQL (mariadb) when cloned to subdomain

cglubish

New Pleskian
Server operating system version
Ubuntu 22.04
Plesk version and microupdate number
18.0.44
Just wiped server, installed Ubuntu 22, Plesk 18.0.44

Cloned a repo to primary domain. Previous DB was mySQL 7, used Plesk to repopulate new mariadb instance. This works good. I *was* having massive performance issues, due to load and some large queries, but added these two lines to my.cnf and things started rolling again.

innodb_buffer_pool_size=3072M
query_cache_size=64M

Next, I cloned the exact same repo to a subdomain, to use as a staging site. Used plesk to import the exact same database. As far as I can tell, every single setting is the same between the main site, and the duplicate in the subdomain. I adjusted a few php settings, but only using the Plesk interface, and the same on both. But the subdomain site is painfully slow, with constant Gateway Timeouts. The logs show "upstream timeout", so I assume its database issues.

I've exhausted my attempts to debug this... no idea where to look.
 
Back
Top