The GC and performance, but not what you expect

[Atila Neves via Digitalmars-d]

I tried modifying the runtime but unfortunately vibe.d doesn't
compile with the latest dmd. I don't feel like fixing it or
figuring out how to compile gdc either. As mentioned later, I
wouldn't be able to claim to beat Java, but I would be able to
see how much faster it would go without the lock, though. Oh well.

Also, there was a bit too much focus on Java on this thread. The
fact is that the C implementation is faster than D as well, and
just as fast as Java.

Atila

On Thursday, 29 May 2014 at 18:42:20 UTC, Ali Çehreli wrote:
> On 05/29/2014 06:06 AM, Steven Schveighoffer wrote:
>
> > The explanation in the comment is that finalizers may spawn a
> new
> > thread. See
> > 
> https://github.com/D-Programming-Language/druntime/blob/master/src/gc/gc.d#L410
>
>
> The strange thing is, finalizers may not even be executed. :-/ 
> I would simply change the spec saying "finalizers may not start 
> a new thread."
>
> Getting back to Atila's issue, I would simply comment-out that 
> lock in druntime, beat Java, and then put the lock back in. :o)
>
> Ali