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.

Sign up for GitHub

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

Jump to bottom

Reduce the scope of the CCW cache or consider lock free #10787

Closed
jeffschwMSFT opened this issue Jul 27, 2018 · 2 comments
Closed

Reduce the scope of the CCW cache or consider lock free #10787

jeffschwMSFT opened this issue Jul 27, 2018 · 2 comments
Labels
area-Interop-coreclr
Milestone
Future

Comments

@jeffschwMSFT
Copy link
Member

In processes that heavy use of COM can have considerable contention on the CCW cache lock. Currently the lock is for the whole process (eg. per-appdomain).
@jkoritzinsky
Copy link
Member

Looks like as part of dotnet/coreclr#20919 the CCW cache was changed to be per-LoaderAllocator instead of per-process.

@msftgits msftgits transferred this issue from dotnet/coreclr Jan 31, 2020
@msftgits msftgits added this to the Future milestone Jan 31, 2020
@AaronRobinsonMSFT
Copy link
Member

Confirmed @jkoritzinsky's observation. I am going to close this issue since the global lock has changed. We can revisit if we hear additional user feedback.

N.B. The new CCW management API will not suffer from this contention - see #32091.

@ghost ghost locked as resolved and limited conversation to collaborators Dec 16, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
area-Interop-coreclr
Projects
None yet
Milestone
Future
Development

No branches or pull requests
4 participants
@jkoritzinsky @msftgits @jeffschwMSFT @AaronRobinsonMSFT