Hello, thanks so much for all your work on Tainacan, it’s such a wonderful resource.
I am having some trouble with a very slow load time on my main collection page: The Clockworks Collection – The Clockworks . It seems to do nothing for a long time and then load all at once.
I’ve looked through the archives on this forum and have seen suggestions to disable faceted views and clear old files via the garbage CLI command - I have done both these things, but it hasn’t made any difference. We also recently changed our hosting provider, which has resulted in much faster load times for the site as a whole, but no change to the Tainacan page.
I wondered if maybe I was missing something else that might be obvious to you guys when you look at it? I’m using the Blocksy theme.
You are likely experiencing the same thing I had here:
The solution is to optimize the WP DB indexes and one plugin I’ve been using on Tainacan and WP in general clients is the “Index WP MySQL For Speed”. It changes the database indexes to a much faster setup. I’ve seen significant improvements on both Tainacan and WordPress blogs and applications that rely on WP tables.
Like any database change, please backup your site and data before trying it. I’ve never had an issue, but it has the potential to break your whole database if anything goes wrong.
Thank you so much! I’ve now installed and activated that plugin, cleared the cache etc - I’m afraid I’m not seeing any improvement so far. Do you know if that plugin is the only way to make this change?
you don ´t have that many rows (my example has about 10x more). It shouldn’t be suffering due to indexes even if that wasn’t the case.
I’d say the issue is within your host. Even though the rest of the site is fast, it may be due to caching on the hosting service configuration (some times even internally). However, Tainacan goes directly through WP, without cache through REST. This is not usually cached and thus has to run full WP execution, going to the DB and all.
If it is a shared environment, that could easily be limiting the resources or even be limited due to low resources. I had an experience on another case unrelated to Tainacan in which the server was “fast” but the disk was very slow. Their internal caching system made most of the calls be quick, but disk intensive tasks like backup were painfully slow. This might be similar to what you have (DB access or CPU may be capped).
I accessed your site and it does have a delay, but I’d say it is not very different from what I’ve experienced in similar situations on shared hosts and even on small cloud hosts.
I´m not sure what else could be improved without going further down the performance rabbit hole (which is usually not possible unless you control the whole server or add something like elasticache to improve search, which is possible on shared hosts but is a separate service).
Yeah 100 items with that short amount of metadata is no good reason for a slowdown, you shouldn’t need even database index tweaks… I do think there might be something in the host side.
And how about your log? Do you have many? Go to your Activities List at the repository level and see how many are there…
