Easy & huge GC optimizations

[Chris via Digitalmars-d]

On Friday, 23 May 2014 at 17:38:27 UTC, Etienne wrote:
> On 2014-05-23 1:29 PM, Chris wrote:
>> I know that CPU's do a good bit of guessing. But that's not 
>> the same
>> thing. If they err, they make up for it ("Ooops, it's not in 
>> the cache!
>> Will get it from HD, just a nanosec!"). If the GC errs, how do 
>> you make
>> up for it? Please educate me.
>
> If the GC errs, worst case you lose a few bytes of free space 
> (Type 1 Error: skips collection for an object). If it weren't 
> already known, the worst case would be that destructors are not 
> guaranteed to be called.. but that's taken for granted now. 
> Worst case will never be access violation even through machine 
> learning

Fair enough. But what about programs that allocate a lot and run 
for ages (a server app for example)?