Recognizing that there are many ways every person’s Omeka Classic/Omeka-S instances vary across servers and networks and architectures, I’m still thinking there is a specific issue with my Omeka-S instance that might be applicable across multiple implementations.
On the same server, which is a decent modern VM but nothing superpowered (anyway I don’t think Apache, MySQL, and Omeka/Omeka-S take advantage of multiple cores or huge amounts of RAM) - in Omeka Classic, the admin/items view page takes a total of 3.3 seconds to load, with a 1.2 second wait before any response (presumably, a SQL query being executed to populate the results).
In Omeka-S, with nearly exact same set of documents (154,520), the admin/items page takes a total of 7.6 seconds to load, with a 5.5 second delay before ANY response (presume the same as above). So, once the query is delivered, both Omeka-S and Omeka Classic take exactly 2.1 seconds to render the page!
But for some reason, Omeka-S has a 5 second delay. Posting the Firefox > Web Developer > Network view screenshots to demonstrate this.
Any suggestions as to what I should check on the server? In the database? On the app config?