Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
GC pressure in CompositionConfiguration even when loading from cache
See original GitHub issueTargeting .NET Framework 4.7.2. First of all, I don’t understand why I see this when loading the MEF graph from disk. Why does it try to find loops when the deserialized graph obviously cannot have any loops?
I see lots of temporary allocations at
CompositionConfiguration.cs(297). It’s like 100 MB of Enumerable.Where<T> that is thrown away, causing unwanted memory pressure.
I believe this can be optimized. I.e. don’t use LINQ, no matter what. If I find time, I’ll try to help out.
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
You’re right. The cache is loaded using
catalogManager.LoadAsync()and then thisCompositionConfiguration.Create()API is called. I guess I need to re-work my caching mechanism to avoid this when loading from cache.Possibly. But a million enumerator allocations would certainly be of importance. We have an enormous amount of exports and imports.