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

VS 16.x tooling performance #6866

Closed
10 tasks
cartermp opened this issue May 25, 2019 · 1 comment
Closed
10 tasks

VS 16.x tooling performance #6866

cartermp opened this issue May 25, 2019 · 1 comment

Comments

@cartermp
Copy link
Contributor

cartermp commented May 25, 2019

This is an overarching issue that we're u sing to track F# tooling performance in VS. I expect these to positively impact other F# editors. Much of this work is actually in the compiler, as some things that are fine in a command-line scenario end up costing us dearly in a tooling scenario.

These are all filed based on data gathered from ETL traces with a solution loaded into Visual Studio, or are related to an issue where data was gathered in this way and determined to also be relevant. other issues labeled Tenet-Performance that are not listed here are not necessarily gathered in this way.

@cartermp
Copy link
Contributor Author

Closing this out now that we have a pretty good hold on VS tooling perf. Still work to do, but boy is it a whole lot better.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants