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
In past an attempt to use shared memory/memory mapped file(on flush not for every hit registration, so we need also to take care of performace against int array) with no luck due to special needs of System.Private.CoreLib#276 (comment), if we take this path maybe we need to avoid such dependency and wrap native api cross plat.
The text was updated successfully, but these errors were encountered:
After a prolific talk with @jakubch1 we could try to change hits report strategy to solve mainly two issue:
Possible solution: we could change tracker to report hits in a shared memory open by out-of-proc data collector.
Possible solution: report hits directly to persisted memory-mapped file https://docs.microsoft.com/en-us/dotnet/standard/io/memory-mapped-files
In past an attempt to use shared memory/memory mapped file(on flush not for every hit registration, so we need also to take care of performace against int array) with no luck due to special needs of
System.Private.CoreLib
#276 (comment), if we take this path maybe we need to avoid such dependency and wrap native api cross plat.The text was updated successfully, but these errors were encountered: