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: resolver - skip cwd lookup if able #23851

Merged
merged 7 commits into from
May 21, 2024

Conversation

dsherret
Copy link
Member

The cwd lookup was taking 2% of a flamegraph I was looking at.

@dsherret dsherret requested a review from bartlomieju May 16, 2024 21:28
Copy link
Member

@ry ry left a 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?

@dsherret
Copy link
Member Author

For what length of time is the cwd cached?

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)

Copy link
Member

@littledivy littledivy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@dsherret dsherret merged commit 54eb930 into denoland:main May 21, 2024
17 checks passed
@dsherret dsherret deleted the perf_skip_cwd_check_if_able branch May 21, 2024 14:38
bartlomieju pushed a commit that referenced this pull request May 21, 2024
The cwd lookup was taking 2% of a flamegraph I was looking at.
bartlomieju pushed a commit that referenced this pull request May 21, 2024
The cwd lookup was taking 2% of a flamegraph I was looking at.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants