-
Notifications
You must be signed in to change notification settings - Fork 5.4k
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: resolver - skip cwd lookup if able #23851
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For what length of time is the cwd cached? Is there a danger of inconsistent behavior if it gets changed?
It should only be using the initial cwd for the main module, which won't have its cwd changed by this point (unless something outside the process races to change the cwd after the initial cwd is stored, which this actually works more as expected now) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
The cwd lookup was taking 2% of a flamegraph I was looking at.
The cwd lookup was taking 2% of a flamegraph I was looking at.
The cwd lookup was taking 2% of a flamegraph I was looking at.