3 ms·
I consider the root cause to be a mis-match between the memory management needs of the application and the assumptions of the GC. Their solution matches the app
by scott_s 15y ago
I consider the root cause to be a mis-match between the memory management needs of the application and the assumptions of the GC. Their solution matches the application's memory usage with the assumptions of the GC.
What would be more useful to them is to be able to provide either hints to the GC, or to actually have some control over memory management. That is, keep the application the same, but let it influence GC behavior. They're forced to go at it the other way: keep the GC the same, but change the application so what the GC does becomes the right thing.
they modify the code in ways that don't represent the semantics of the problem to work around a limitation of the implementation.
That is always true when you start optimizing for performance. And nick_craver explains why the proposed suggestion may be easier to say, but there are hidden complexities. Personally, once you start introducing external control to your application like that, alarm bells go off in my head.