This repository has been archived by the owner on Sep 30, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Completely resolve indexed search performance regression in v3.2.0 (#…
…4048) * search: completely resolve indexed search performance regression in v3.2.0 In #3685 I resolved a major indexed search performance regression that was introduced in v3.2.0. For a search returning 100 repositories and 100 results per repository: 1. After the regression: we would do 100*100 == 10,000 Git OID resolutions (which would overload Gitserver and cause searches to timeout) 2. After my previous resolution, we would no longer do duplicate work and thus only did 100 Git OID resolutions (1 per repository). - This was shown in benchmarks and load tests on customer instances to be a substantial improvement. - On one customer instance, we've found this still hasn't been enough of an improvement. - On another customer instance, we've found we could be doing better. 3. After *this* resolution, we are 100% at the performance level we were at prior to v3.2.0 because we are no longer doing *any* additional Git OID resolutions. Zoekt already has this information and we already aquire this information prior to executing searches, we just weren't correctly reusing this information. Should fully resolve an outstanding issue https://app.hubspot.com/contacts/2762526/company/464956351 is facing. Helps https://app.hubspot.com/contacts/2762526/company/407948923 * remove now unnecessary Git OID resolution & caching logic * CHANGELOG * fixup reversion * fixup * update tests
- Loading branch information
Showing
13 changed files
with
113 additions
and
468 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.