Home › Forums › Product Support Forums › Ajax Search Pro for WordPress Support › Search is slow to the point of being unusable
- This topic has 4 replies, 2 voices, and was last updated 8 years, 2 months ago by
arnonzamir.
-
AuthorPosts
-
March 9, 2018 at 10:49 am #17055
arnonzamir
Participantsearch is painfully slow.
it takes 15-30 seconds to get a result.
I went through all the caching, indexing and the custom ajax handler.
March 9, 2018 at 11:08 am #17056Ernest Marcinko
KeymasterHi,
Something seems to be conflicting there, as the page load seems to be fine.
Can you please check the back-end details? I am not able to log-in with them.
I will most likely also need FTP details for this one, as I will have to debug through the code to see where the issue is.Thanks!
March 9, 2018 at 12:00 pm #17060arnonzamir
ParticipantYou cannot access this content.
March 9, 2018 at 12:38 pm #17063Ernest Marcinko
KeymasterHi,
Okay, so you have over 50 000 posts there, and the index table was 5 million records long, that is huge. The server was simply not able to process the query on such a huge amount of data.
I have found a possible configuration that will likely work the best for you:
– First, I have cleared the index table, so that no unneccessary records are being stored.
– Then I changed back to the regular engine, and only enabled the search in titles: https://i.imgur.com/elE1P5t.png
The post title fields in WordPress are indexed already, that is why I decided to switch from the index table. And since you have over 50 000 posts, searching the contents is not neccessary, as the titles will almost surely yield enough results.
– I also disabled the secondary logic, to gain even more performance boost: https://i.imgur.com/5p2a2x9.pngNow it yields almost immediate results.
This is a really solid configuration in my opinion. If you want to switch back to the index table engine, you can – just make sure to re-create the index, and only enable to index the post titles – as the database will not be able to process the query for 5 million records in the content fields, it is too much for the server to handle.
I have also temporary disabled the log and query log plugins you had. I have re-enabled them now. I strongly recommend turning those off once you are done with debugging, they can impact the server performance negatively.
March 9, 2018 at 1:07 pm #17064arnonzamir
ParticipantThanks – it is significantly faster this way. I am not sure that this will be enough for the client but I will try – they are very into full text search.
-
AuthorPosts
- You must be logged in to reply to this topic.