I just did a test to implement site search on a mostly empty trialsite and site search was very very slow. I had a 76s TCP response and 194s onload event.
Are others experiencing this? Do you have workarounds? Could it be an implementation issue? I just inserted the default search form on an empty page and there are probably only 20 items total across all modules/pages/forms on this test site.
I also noticed that on the Docs demo site search was very slow. In the range of 30s for search results.
Docs Demo site seems to be fine now, perhaps was a temporary issue?
But one thing to make sure is that your search results page is marked as ‘Disable From Site Search’ otherwise you can get a recursion issue if it includes itself in the results.
The Docs site is slow overall, yes. This is being worked on.
However, site search in general I’m not experiencing any slow loading for (on various other sites).
Are you still seeing slow results on the Docs Demo Site?
Are you seeing slow search results on any of your sites?
Hey @Adam.Wilson, yes the docs site search is very slow for me still. I just did a search and it took a while to return a result (16s).
I don’t have search on any live sites yet, but I will have to as I get ready to migrate over/build ecomm sites. I was doing some research last week and I had some serious concerns. I have a test site with almost nothing on it. I used the default search form, nothing customized, and search was taking a looooooong time.I’ve got a ticket into support and they’ve been looking into it. As I test it today it’s not too bad, it’s about 5 seconds to return results in a basically empty set. I wonder how this would be if I had a set of 1000 or 5000. Any experience with this? Does search set size effect result speed?
What is that syntax? I’ve noticed similar syntax in migrated site, but never really stopped to look into it. There seems to be a secondary module call syntax that’s generated by the migration app. Is there documentation on this anywhere?
@Alex_B_Centrifuge I don’t think that is what @Adam.Wilson means. It’s about a problem (not only with module but also with site search) I had for a while. To display search results you would usually do something in your list layout like:
This should actually only render the first 20 words of the page’s content in plain text, but if there’s a liquid module tag within this first 20 words, it will render the module hence spoiling your results.
I found that I can avoid that by using this list layout code:
Basically, it’s the same as applying isSearchResult to a component tag but where isSearchResult looks for search parameters in the URL, searchScope instead is coded directly into the component parameter. So it can be hard-coded or dynamically constructed with Liquid variables without the need for passing URL params.