Optimize pack readHeader() implementation #1574
Merged
Conversation
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
Load pack header length and 15 header entries with single backend request. This eliminates separate header Load() request for most pack files and significantly improves index.New() performance. Signed-off-by: Igor Fedorenko <igor@ifedorenko.com>
ifedorenko
force-pushed
the
1567_optimize-pack-readHeader
branch
from
6e299a6
to
953f3d5
Compare
ifedorenko
commented
Jan 24, 2018
| const maxHeaderSize = 16 * 1024 * 1024 | ||
|
|
||
| // we require at least one entry in the header, and one blob for a pack file | ||
| var minFileSize = entrySize + crypto.Extension | ||
|
|
||
| // number of header enries to download as part of header-length request | ||
| var eagerEntries = uint(15) |
There was a problem hiding this comment.
@fd0 This number is based on stats from single 435GB repository (where >98% of all packs have 15 or less header entries, fwiw). Maybe useful to get stats from other repositories, assuming you have access or have interested users who can provide the info.
|
|
||
| return binary.LittleEndian.Uint32(buf), nil | ||
| } | ||
|
|
||
| const maxHeaderSize = 16 * 1024 * 1024 | ||
|
|
||
| // we require at least one entry in the header, and one blob for a pack file | ||
| var minFileSize = entrySize + crypto.Extension |
There was a problem hiding this comment.
Not related to my change, but I believe minFileSize should be 4 bytes longer to account for header length record at the end of the file.
fd0
added a commit
that referenced
this pull request
Jan 24, 2018
Optimize pack readHeader() implementation
fd0
added a commit
that referenced
this pull request
Jan 24, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What is the purpose of this change? What does it change?
Load pack header length and 15 header entries with single backend
request. This eliminates separate header Load() request for most pack
files and significantly improves index.New() performance.
Was the change discussed in an issue or in the forum before?
See #1567
Checklist
changelog/x.y.zthat describe the changes for our users (template here)gofmton the code in all commits