Skip to content

Fix grammar issues in faster search blog post #373

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.

Sign up for GitHub

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

Merged
stsewd merged 2 commits into from
Feb 3, 2026
Merged

Fix grammar issues in faster search blog post #373

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
c3214fb
Initial plan
Copilot Feb 3, 2026
ecd7acf
Fix grammar issues in blog post
Copilot Feb 3, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions content/posts/faster-search.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -116,8 +116,8 @@ this enables [HTTP compression and other optimizations](https://www.elastic.co/g

Query times dropped from **60ms to 25ms** on Community and **60ms to 40ms** on Business.

Note: The difference in improvement between Community and Business is likely due to difference of the instance type used in each platform.
On Community, we use a more powerful instances due to the higher storage needs.
Note: The difference in improvement between Community and Business is likely due to the difference in the instance types used in each platform.
On Community, we use more powerful instances due to the higher storage needs.

## Conclusions

Expand Down Expand Up @@ -180,7 +180,7 @@ While we are happy with the improvements we have made so far, there is still roo

- Revisit the number of shards.
We decided on the number of shards based on the size of the index before re-indexing,
but the resulted index was smaller than we expected (there was maybe some fragmentation on the old index).
but the resulting index was smaller than we expected (there was maybe some fragmentation on the old index).
Reducing the number of shards could improve performance, but it's not clear by how much.
As this requires re-indexing again, we won't do this unless we need to re-index for other reasons.
- Further optimize database queries.
Expand Down