This repo contains CoreRT, an experimental .NET Core runtime optimized for AOT (ahead of time compilation) scenarios, with the accompanying compiler toolchain.
Based on the code only a few of the GC settings can currently be configurated with the rhconfig.ini file. While someone can make changes in gcconfig it fells like a bad hack for me. In the long run I assume it's not the plan to compile a new run time for every project.
I am not sure how much improvements you can be get by tweaking some GC settings on a desktop system but at least on some game consoles I noticed significant performance improvements by using GCLargePages and GCHeapHardLimit. And with a fixed size memory pool it makes sense to limit the size of the memory the GC can use anyway.
Any objections to support more settings in rhconfig.ini?
Based on the code only a few of the GC settings can currently be configurated with the rhconfig.ini file. While someone can make changes in gcconfig it fells like a bad hack for me. In the long run I assume it's not the plan to compile a new run time for every project.
I am not sure how much improvements you can be get by tweaking some GC settings on a desktop system but at least on some game consoles I noticed significant performance improvements by using GCLargePages and GCHeapHardLimit. And with a fixed size memory pool it makes sense to limit the size of the memory the GC can use anyway.
Any objections to support more settings in rhconfig.ini?