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

Remove DocumentWithOptions and pass around DocumentIds #695

Merged
merged 1 commit into from Jun 1, 2020

Conversation

JoeRobich
Copy link
Member

Resolves #691

@JoeRobich
Copy link
Member Author

JoeRobich commented Jun 1, 2020

Anecdotally this improves performance

Integration Run Before Changes
image

Integration Run With Changes
image

Copy link
Contributor

@jmarolf jmarolf left a comment

Choose a reason for hiding this comment

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

:shipit:

@JoeRobich JoeRobich merged commit 61e5536 into dotnet:master Jun 1, 2020
@tiesmaster
Copy link

@JoeRobich As a lurker in this repo, I saw this PR coming by, and I was just curious why the integration steps take this long, so I was looking into the integration tests, and what takes up its time. Opening up azure-pipelines-integration.yml, I noticed that both this repo, as Roslyn have the same hash reference (which of course cannot happen with git).

Looking at the pipeline task, I also see it fails on the checkout, so you might want to look at that.

@JoeRobich
Copy link
Member Author

@ tiesmaster Thanks for lurking!

I was just curious why the integration steps take this long

image

Roslyn is definitely the long pole in the integration tests.

The prepare step which takes over a third of the time, is where we clone the repo, checkout the SHA we want to target, and restore all the solutions we discover. It is possible we can improve on the cloning by only checking out the SHA we care about with a depth of 1 (see https://stackoverflow.com/a/43136160).

The second longest step is Running format against the Roslyn.sln. This can be painful because there are, at last count, over 170 projects referenced. So it takes a while for the design time builds to complete so that we know which files are part of the solution. Loading fully from a design time build also provides us with the semantic information we will need to run analyzers and fixes in the future. In addition we also run against the Compiler.sln, so a double whammy there.

I noticed that both this repo, as Roslyn have the same hash reference (which of course cannot happen with git).

Thanks for spotting this. Cut and paste strikes again =)

@JoeRobich JoeRobich deleted the refactor-documentwithoptions branch March 5, 2021 21:02
vdurante pushed a commit to vdurante/format that referenced this pull request Feb 29, 2024
…ions

Remove DocumentWithOptions and pass around DocumentIds
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.

Refactor out the DocumentWithOptions type
3 participants