Describe the problem you would like to solve
Our editors need a way to publish journal issues with dozens of items without losing performance.
Describe the solution you’d like
Asynchronous page loading would allow the visitor to navigate the site without much waiting. For example: if a page contains 100 articles, the visitor could start browsing when 10 articles are already available and not when all 100 have been loaded.
Who is asking for this feature?
Journal Editors, Journal Administrators and readers.
Async and Virtual scroll should be enough to suggest the way forward.
November 29, 2022, 11:47am
are you talking about the table of contents of the issue, or the editorial backend?
I’m talking about the table of contents of the issue in the public portal.
This is an example where, to load the page, you need to wait about 10 seconds.
Thanks and best regards,
November 29, 2022, 2:29pm
I think PKP developers are already aware of this. At least I found and issue one Github mentioning the loading times for large table of contents:
08:55PM - 28 Dec 20 UTC
We published conference proceedings in OJS. When we updated one of them to OJS 3
… .2.1-2, access to the table of contents became extremely slow. We note that there is no specific SQL that takes too long, but the number of SQL queries is high.
Nothing appears until all queries are completed, and the sum of them plus PHP processing is a bottleneck.
- Editions with more than 300 published papers take almost 2 minutes to load
- Access is quick if you go directly to the page of each paper or other than the table of contents
- OJS installations with fewer items published per edition on the same server work at the expected speed.
do you run the DB on a remote server or locally? That can make quite a difference.
discussion here (for various reasons, not only policy, I prefer a professionally 7/24 managed remote DB server with failover (primary/replica or cluster) and backups).
As another option, you could also install the
OjtRocket plugin, until the DB libraries are optimized by PKP.
Hi, thanks for your help!
We have already tried the OjtRocket plugin, but there was no improvement.
The database is local, not remote.
All the conditions seem to be in place, but with that (content-rich) page keeps charging slowly.
I will update you as soon as I have news.
November 30, 2022, 7:14pm
The idea is interesting, but I think you are attacking the symptom rather than the disease.
Have you tested how the magazine behaves with the new 3.3?
One of the lines of work of PKP’s technical committee is to detect problems like this and propose solutions.
I’m passing on the scenario to see if we can reproduce it.
We currently have version 3.2.1-1. We are planning the update, as soon as I have news I will update you.