Skip to content
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

docs: mention the gitgrep backend in the Performance section #150

Merged
merged 1 commit into from
Feb 27, 2025
Merged

docs: mention the gitgrep backend in the Performance section #150

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
3 changes: 3 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -202,6 +202,9 @@ Generally performance is very good, but depending on the size of your project
and your computer's specifications, the search can be fast or slow. Here are a
few things you can do to improve performance:

- Use the experimental git grep backend by setting the
`future_features.backend = "gitgrep"` option (see above). This can be faster
in medium/large projects.
- Set the `prefix_min_len` option to a larger number avoid starting a search for
very short words. This can prevent unnecessary searches and improve
performance.
Expand Down
Loading