Hi @xden0006,
OJS is known to execute a lot of SQL statements, and this can affect performance on large datasets, particularly in cases where the database server is not hosted on the same machine as the application.
If your database server is not on the same machine as the application, I would suggest moving it there – you’ll immediately see a significant performance improvement.
Meanwhile, we are working gradually on improving performance by applying a variety of improved storage layer techniques. Significant work is already included in OJS/OMP/OPS 3.5.0, which was very recently released and will become our next LTS (Long-Term Support) line of releases. However, this isn’t a 100% complete solution, as at least one user with a very large database has reported performance issues with 3.5.0.
Any improvements we do make – short of something trivial like adding an index on a table – will be to 3.5.0 or 3.6.0. I’d suggest testing 3.5.0 to see if it offers some improvement, as a starting point.
Regards,
Alec Smecher
Public Knowledge Project Team