-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
A Few Thoughts on a Large Site #4
Comments
I am interested in this approach of searching. If you implement this functionality, how would you handle this kind of problem, @lgrrealag ? My only viable solution is to use more compact document format like JSON and not including all post content. |
i think json will help but the only way this will work for a medium to large site is adding the ability of choosing what to expose, maybe just titles and short content |
Hello. Was this issue solved already? I am curious. |
Looks like this can be solved with xpath filters as the XML is being saved? |
Came across your plugin and was optimistic that perhaps it could solve some of the problems with WP search. Running a few tests on one of our test sites has provided me with some information that I would pass on for you to consider.
Had problems activating the plugin. PHP log showed it was running out of ram. Increasing the ram to 1gb of ram for WP solved that issue. Most likely related to the fact that it is a large website. We have just over 10k posts and well creating the search xml file with the base amount of 256mb of ram was not enough.
The plugin was created to offer search to WP sites that were turned static, so the search uses the xml file of the posts to search. Great idea, except with large sites that file is HUGE! Our search xml file was 170mb uncompressed. Since the search then loads that file on every page load, even delivering it gzipped it was roughly 15mb extra on every page load. That is not really practical on a site. If you only have a few hundred posts sure but the overhead of having to load the search xml file is to much. Perhaps if it was only loaded when the search box was in focus or some other way it would cut down on that extra download, but still really only good for maybe 1k posts.
3, Perhaps because the search xml file is so large in our test case but could not get the script to even return any results.
Anyways, interesting idea but not really practical for large sites.
Good luck.
The text was updated successfully, but these errors were encountered: