perf(normalization): Optimize path normalization #57570
Open
Conversation
This file contains hidden or 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
Signed-off-by: Carl Schwan <[email protected]>
CarlSchwan
force-pushed
the
carl/perf/normalized-path
branch
from
76ac2f8 to
940e5bf
Compare
CarlSchwan
requested review from
come-nc,
leftybournes,
provokateurin and
yemkareems
and removed request for
a team
Merged
Altahrim
approved these changes
Jan 16, 2026
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.
Summary
Remove caching since when we request path normalization for more entries than the cache size, it's useless and is quite expensive
When doing a PROPFIND on the root, decrease memory usage from normalizedPath but increase it a bit on normalizedUnicode
TODO
Checklist
3. to review, feature component)stable32)