Funny, I wrote an almost similar post, but then decided I was not in the right to share your data on the forum, so I added it to a draft email.
I then decided to also run a test with your code, so I decided not to send it. I added my email below, but yes, I agree, I think this is a CLR “issue” and I just .NET that is used to things using more RAM.
Just a quick catch up.
- I see OpenFlow has been running non-stop for more than 7 days.
- I need to conclude the memory “issue” is a .NET CLR issue and not an error in my code. Here is the last 7 days with your own code in your environment:
That non-stop increase over multiple days hurts my eyes. I don’t like it, but I saw the same in my own tests until I told the CLR to stop overcommitting. Here is a 3-day non-stop test in my environment, and it does stabilize either way:
I am 99.9% sure adding the runtimeconfig.template.json will help. Here is my test with runtimeconfig.template.json added to the code you shared with me:
( i wanted to wait some hours or a day before taking the last screenshot and send it but still looks like it starts out much lower )