You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
CoreClr is able to use object header bits for locking in trivial cases. That makes typical use of lock fairly cheap. NativeAOT does not have that and lock(obj) is always a "fat lock".
This is likely the reason for regressions in ConcurrentDictionary benchmarks.
(re: #68891)
The text was updated successfully, but these errors were encountered:
@tomcashman this is already in progress, sorry.
There is already an implementation at a stage where I know it is correct (as in "passing all tests"), but I do not know yet if the perf is acceptable.
CoreClr is able to use object header bits for locking in trivial cases. That makes typical use of
lock
fairly cheap. NativeAOT does not have that andlock(obj)
is always a "fat lock".This is likely the reason for regressions in ConcurrentDictionary benchmarks.
(re: #68891)
The text was updated successfully, but these errors were encountered: