Improve search index performance with lazy loading and compression
Maintainers usually reply within 3 days
@seansica is already working on this.
Since Apr 20, 2023.
Assessment
This issue has not been assessed yet.
Description
The current search solution for a website involves a FlexSearch Document that has two search indexes for page titles and content. This is used to index around 3704 objects on 1852 pages. It takes approximately 5-6 seconds to index all objects using the SearchService.initializeAsync method, which causes a noticeable delay for website visitors when the website is loaded for the first time.
The delay is caused by two things: downloading the JSON files containing the index-able items and the time it takes to index them in the FlexSearch Document. However, the delay only persists the first time a user visits the website because the search index and the index-able items are cached in IndexedDB, which allows the search index to be restored without having to re-download the items and re-generate the search index.
To improve the user experience, we can potentially reduce the time it takes to generate the search index by assigning each search index to a web worker and increasing the number of search indexes. This will enable lazy loading of search results as they are returned from each individually threaded search index, resulting in an improved user experience because results can be rendered as they are yielded. This is faster than generating and querying one massive search index.
Additionally, we can potentially reduce the time incurred from downloading JSON files by reducing the size of the files and using compression.
- Dominant language
- HTML
- Stars
- 590
- Forks
- 175
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 3
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from mitre-attack/attack-website
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
mitre-attack/attack-website#628 · 1 comment ·
Maintainers usually reply within 3 days
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
mitre-attack/attack-website#626 ·
Maintainers usually reply within 3 days
-
Difficulty 3/5 1-2 days Newbie friendliness 52/100
mitre-attack/attack-website#596 ·
Maintainers usually reply within 3 days
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
mitre-attack/attack-website#571 · 2 comments · 1 reaction ·
Maintainers usually reply within 3 days
-
[Accessibility] Navbar logo missing alt text causing WCAG violationMay be free again @jondricek claimed this 233 days ago, and no pull request is open. Open
mitre-attack/attack-website#563 · 1 assignee ·
Maintainers usually reply within 3 days