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.

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

PERF: reduce PSI tree access in very hot item resolution #4210

Merged
merged 1 commit into from Aug 5, 2019

Conversation

vlad20012
Copy link
Member

@vlad20012 vlad20012 commented Aug 1, 2019

This speeds up highlighting up to 5% (the baseline is before #4179)

The approach is similar to #4182 - make more things accessible by one cache key and retrieve them together to reduce PSI (in the case of this PR) and cache access in very hot code.

@Undin Undin added the fix Pull requests that fix some bug(s) label Aug 5, 2019
@Undin Undin added this to the v103 milestone Aug 5, 2019
@vlad20012 vlad20012 force-pushed the perf-name-resolution-cached-items branch from 6a9be94 to 279d096 Compare August 5, 2019 15:04
@vlad20012
Copy link
Member Author

bors r+

bors bot added a commit that referenced this pull request Aug 5, 2019
4210:  PERF: reduce PSI tree access in very hot item resolution r=vlad20012 a=vlad20012

Depends on #4190

This speeds up highlighting up to 5% (the baseline is before #4179)

The approach is similar to #4182 - make more things accessible by one cache key and retrieve them together to reduce **PSI** (in the case of this PR) and cache access in very hot code. 

Co-authored-by: vlad20012 <beskvlad@gmail.com>
@bors
Copy link
Contributor

bors bot commented Aug 5, 2019

@bors bors bot merged commit 279d096 into master Aug 5, 2019
@bors bors bot deleted the perf-name-resolution-cached-items branch August 5, 2019 16:21
@Undin Undin added this to Done in To test Aug 7, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
fix Pull requests that fix some bug(s)
Projects
To test
  
Done
Development

Successfully merging this pull request may close these issues.

None yet

2 participants