Frameless output search performance - successful solutions?
Hello,
Our support team has reported numerous search performance issues with the search performance in generated Frameless output. The issues reported by them are:
- Enter a search term OR pick a suggested search term from predictive text
- Click the find icon to start the search
- Wait for the search to execute
- Search takes a very long time to return results (120+ seconds) OR the browser returns a "Not Responding" error and prompts the user to reload the page
The issues occur across browsers and OS's. We've received reports on Chrome, Firefox, Safari, and Edge, all on the latest versions.
I have reviewed the two existing threads detailing similar performance issues:
https://community.adobe.com/t5/robohelp/frameless-search-performance-issue/m-p/10863150
https://community.adobe.com/t5/robohelp/home-page-search-stopped-working/m-p/10948361
However, the solution there seems to be "update to the latest version of RoboHelp and regenerate the output". This has not so far resolved the issue, as the performance issues persist.
What specific steps after updating Robohelp have people done to succesfully address the issues? I would appreciate any guidance. If I need to recreate the project from scratch to force a reindex, so be it, but I am hoping for a different solution
Additional details:
- Robohelp version: 2020.3.32
- OS: Windows 10
- Search performance is markedly improved on local files, but will crash the browser when on a web server
- Review in Chrome Devtools shows that some files spend a long time waiting for download
- Search for the search term in the output files via Notepad++ shows that problematic search terms are present in files more than the 25-30 occurrence threshold reported in the linked threads
- Asian languages seem disproportionately affected, but this may be due to higher usage of the localized help content in the APAC region
AdChoices