- This topic has 7 replies, 2 voices, and was last updated 9 years, 8 months ago by
.
Viewing 8 posts - 1 through 8 (of 8 total)
Viewing 8 posts - 1 through 8 (of 8 total)
These forums are now closed and remain for historical purposes.
None of the content applies to the new version 3. For support, get in touch via our contact form.
Forums › Forums › Search & Filter Pro › 502/timeouts with large amounts of data
Trevor.
Hi,
I have Search and Filter Pro set up on http://shopwomenowned.com/directory. It is set to query a custom post type (businesses) and to allow filtering/search by keyword + 3 taxonomies. The custom post type currently has 126,201 records. The taxonomies have 3, 646, and 636 terms in them. wp_search_filter_cache has 217,081 rows and wp_search_filter_term_results has 1299 rows.
I can load the directory page with just the keyword search and the taxonomy with only three terms. It loads, although slowly (much more slowly than the rest of the site). If I add the two taxonomies with the 600+ terms, the page will time out.
It looks like the issue is coming from the set_filter_term_ids_post_query function, in the Search_Filter_Cache Class and it is taking roughly 100 seconds to finish. See image at http://shopwomenowned.com/wp-content/uploads/2016/06/unnamed.png
Is there anything that can be done to improve the query function to work with large amounts of data or cannot the plugin just not handle it?
Thanks.
That volume of data WILL cause issues with caching. In the settings, have you got caching speed set to slow, medium or fast? Handling larger volumes of data is something we are working on, for the medium or longer term of the plugin. Of course, your server setup will also have an impact.
You appear to be hosted with rackspace.com in Texas, and I can see a few other domains (10-20 maybe) on the same server.
But when I speed test the website, it has an incredibly slow TTFB (Time to First Byte), and I tested it from within the same data center. It has over 3 seconds, whereas my own dedicated server in Kansas is less than a tenth of that (and mine is not an expensive server).
Building a cache like this will require repeated hits to the database, which will be on the hard drive. If the server has a physical hard disc system (RAID or single drives), this will be slow. If, like my server, it has SSD drives, then it will be a lot faster. The amount of RAM available to PHP and WordPress will also affect how much data can be prefetched from the database.
The site is hosted on WP Engine.
The cache is built. My issue is completely unrelated to building the cache, but is related to loading the custom post type archive with the search/filter widget in the sidebar when the taxonomies with 600+ terms are included as a filter.
Missed you again. I’m in the US, mountain time zone. I could do it either at 8:30 AM mountain time or after noon mountain time. I’m guessing the 8:30 AM time will work better with your support hours.
My skypename is amberhinds.
If that doesn’t work, I can also make a screen cast tomorrow.