Skip to content

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

Closed

Description

@jeffschwMSFT

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).

Activity

  1. jkoritzinsky commented on Mar 26, 2019

    @jkoritzinsky
    Member

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

  2. transferred this issue fromdotnet/coreclron Jan 31, 2020
  3. added this to the Future milestone on Jan 31, 2020
  4. AaronRobinsonMSFT commented on Feb 17, 2020

    @AaronRobinsonMSFT
    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.

  5. ghost locked as resolved and limited conversation to collaborators on Dec 16, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions