Short answer

Performance can change after an upgrade because of configuration differences, database connection behavior or server resource pressure. Start with a controlled check of the changed configuration and local database connection, then review server resources and logs.

In this article

Start with the database host setting

In sanplex/config/my.php, review whether the database host is configured as localhost. Changing it to 127.0.0.1 can avoid local hostname resolution delays in some environments.

Check the main performance areas

  • Compare configuration files and deployment settings with the pre-upgrade version.
  • Check whether redundant code or files from the previous version remain in the deployment directory.
  • Monitor server CPU, memory, disk space and database response during a slow request.
  • Review Apache, PHP, database and Sanplex logs for repeated errors or long-running requests.

Escalate with evidence

Record the URL or action that is slow, the time it takes and any errors from the logs. That information makes it easier to identify a version-specific issue or involve Sanplex support.

Note: Avoid random tuning changes. Adjust one setting at a time so you can verify whether it resolves the slowdown.