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
We should park the other competing threads until the first thread will compile the cached expression. Maybe using ManualResetEventSlim or similar mechanism.
The text was updated successfully, but these errors were encountered:
Given the current pipeline #199 (comment) and the performance numbers we may consider to compile delegate by the first thread and proceed to interpret by the competing threads until the delegate is available.
It seems a better option because only one thread will slow down, others will be responsive. Then eventually all threads will benefit from the compiled delegate speed-up. Even better that we don't need any blocking synchronization.
* fixing keyed cache #205 results and fixed#208
* first compiling draft for the #101
* fixed spelling in DIZero readme
* added ResolveGenerated to Resolve
* ResolveGenerated for the keyed service
fixing CI - removing System.Diagnostics.CodeAnalysis.ExcludeFromCodeCoverageAttribute
* added ResolveMany and the passing test for the Example
* rc
* moar
* renaming and package related stuff
* tests WithoutFEC
* fix source package
* add smarter initial factory id
* fix net40 target
* WIP adding to the ASP .NET Core sample the CompileTimeDI
* added troubleshooting tip
* moving the DIZero stuff to CompileTimeDI folder including example
updating release notes
* added Asp NET Core 3.1 Mvc example - WIP
* cleanup
Found in #205
We should park the other competing threads until the first thread will compile the cached expression. Maybe using
ManualResetEventSlim
or similar mechanism.The text was updated successfully, but these errors were encountered: