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
Current implementation uses Monitor for internal synchronization but native Task is significantly superior and allows better optimization.
Problem
Monitor allows simple scenarios with multithreaded access but fails in more advanced cases. It also does not allow proper async/await implementation and creates performance overhead
Solution
Lifetime managers could be converted to use Task as internal medium for storage and synchronization.
Impact
TBD.
The text was updated successfully, but these errors were encountered:
ENikS
changed the title
Convert LifetimeManagers to use Task<object> as synchronization mechanizm
Convert LifetimeManagers to use Task<object> instead of Monitor
May 9, 2019
ENikS
transferred this issue from unitycontainer/abstractions
Jun 16, 2019
Description
Current implementation uses Monitor for internal synchronization but native Task is significantly superior and allows better optimization.
Problem
Monitor allows simple scenarios with multithreaded access but fails in more advanced cases. It also does not allow proper async/await implementation and creates performance overhead
Solution
Lifetime managers could be converted to use Task as internal medium for storage and synchronization.
Impact
TBD.
The text was updated successfully, but these errors were encountered: