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(moduleGraph): resolve dep urls in parallel #12619

Merged
merged 3 commits into from Mar 29, 2023

Conversation

sun0day
Copy link
Member

@sun0day sun0day commented Mar 27, 2023

Description

Resolve deps' URLs in parallel in ModuleGraph.updateModuleInfo.

I tested this pr perf both in sapphi's repo and mine, there will be 10-50ms faster in the startup.

Additional context


What is the purpose of this pull request?

  • Bug fix
  • New Feature
  • Documentation update
  • Other

Before submitting the PR, please make sure you do the following

  • Read the Contributing Guidelines.
  • Read the Pull Request Guidelines and follow the PR Title Convention.
  • Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
  • Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
  • Ideally, include relevant tests that fail without this PR but pass with it.

@stackblitz
Copy link

stackblitz bot commented Mar 27, 2023

Review PR in StackBlitz Codeflow Run & review this pull request in StackBlitz Codeflow.

@bluwy bluwy changed the title perf(ModuleGraph): resolve dep urls in parallel perf(moduleGraph): resolve dep urls in parallel Mar 27, 2023
@bluwy bluwy added the performance Performance related enhancement label Mar 28, 2023
bluwy
bluwy previously approved these changes Mar 28, 2023
)
} else {
imported.importers.add(mod)
nextImports.add(imported)
Copy link
Member

Choose a reason for hiding this comment

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

I think it would be a good idea to keep the nextImports in the same order as before, at least to help with debugging and to make the runs more stable.

We could await for the result of Promise.all and then add that to nextImports in order.

Copy link
Member Author

Choose a reason for hiding this comment

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

done

@patak-dev patak-dev merged commit 4823fec into vitejs:main Mar 29, 2023
12 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
performance Performance related enhancement
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants