hmm but only if a GC is programmed as the BM one: Enforced minimalistic RAM usage instead of "pool and don't cut the pool size as long as there is remaining ram" like .NET and other managed environment handle it.
There is no reason to restrict pool size to < than available ram anyway ... beside "let an app look better in numbers" ... but to me, performance counts more than low memory usage and that would allow a significant speed gain if the GC did not cut the poolsize unless its needed. (C# + managed DirectX shows that point quite good ... its not significantly slower than C++ + DX but it is worlds easier to handle, program and design)
There is no reason to restrict pool size to < than available ram anyway ... beside "let an app look better in numbers" ... but to me, performance counts more than low memory usage and that would allow a significant speed gain if the GC did not cut the poolsize unless its needed. (C# + managed DirectX shows that point quite good ... its not significantly slower than C++ + DX but it is worlds easier to handle, program and design)