Closed itadapter closed 7 years ago
Dmitriy, thank you, assuming this is the issue I logged last week.
@realisable
Get NFX from here. (not in Nuget) Build and see how it works in your case.
Add this to your app entry point (in the Main() method), before app container constructor:
App.SetMemoryModel(App.MemoryUtilizationModel.Tiny);
This should get rid of the buffering of references in thread pools. Let me know if I can close this issue
revised, added TRIM on TLWirteSTream in 829b4a8
Closing @realisable
Need to add auto-trim ability to cap the large graph. The case when a customer serializes a huge graph - leaves the refPool with 100s of thousands of instances dangling on the heap.
Need to introduce MAX_REF_POOL_CACHE_ENTRIES and say cap at 1000 or something like this