The GC is the only thing I strongly dislike about the .NET ecosystem. I would really like some option to turn it off altogether (like what Java offers).
I've got several short-lived applications that are extremely latency sensitive and would work flawlessly this way.
I've not had luck with either. The application may allocate more than a single GC segment worth, so the best workaround is to detect an imminent GC and migrate the workload. Unfortunately, migration would incur even more severe penalties than a typical gen2 collection.
I've got several short-lived applications that are extremely latency sensitive and would work flawlessly this way.