-
Notifications
You must be signed in to change notification settings - Fork 331
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
Assembly Resolver perf improvement #1218
Assembly Resolver perf improvement #1218
Conversation
…ldnt be resolved. It is giving ~3.1 seconds perf improvement for 10k xunit tests from vstest.console during execution.
…pta/vstest into assemblyResolverPerfFix
|
||
return null; | ||
this.resolvedAssemblies[args.Name] = null; |
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.
Add this at line:112, because there is exit path at 126 and we should operate on resolvedAssemblies inside lock (this.resolvedAssemblies)
block.
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.
Its already under lock block. As per discussion, added this statement in one catch block.
|
||
return null; | ||
this.resolvedAssemblies[args.Name] = null; |
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.
Add EqtTrace.IsInfoEnabled check for main flows.
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.
Done
…pta/vstest into assemblyResolverPerfFix
Adding null in resolvedAssemblies dictionary for assemblies which couldn't be resolved.
It is giving ~3.1 seconds perf improvement for 10k xunit tests from vstest.console during execution.