On September 3, we migrated OJS 2x to 3x. After that, users have constantly complained about the poor performance of the new version.
See how it is reading in the MySQL database after the migration. MySQL is the same as previously used in version 2x.
See that the increase takes place exactly on the day of release of the 3x version.
OJS 3.x is a more complex application and some of its features (e.g. versioning) will simply take more resources. If you’re encountering performance problems, it would help to isolate areas where it’s causing problems. For example, is a particular area of the system seeming to demand more resources than is reasonable?
Regards,
Alec Smecher
Public Knowledge Project Team
Hi @asmecher,
I appreciated your comments. What we did was:
increase the number of CPUs
Increase memory
These not solved the problem.
I sent an email to all the Editors of the journals, notifying them that I was trying to find the problem. 15 minutes after my email, the server returned to its normal state:
After email:
Monthly consumption:
I’m trying to identify if a plugin has been disabled and if it was causing this excessive consumption.