[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [computer-go] Pattern Matcher




> -----Original Message-----
> From: computer-go-bounces@xxxxxxxxxxxxxxxxx
> [mailto:computer-go-bounces@xxxxxxxxxxxxxxxxx]On Behalf Of Vincent
> Diepeveen
> Sent: Monday, November 08, 2004 21:58
> To: drd@xxxxxxxxxxxxxxxxx; computer-go; computer-go@xxxxxxxxxxxxxxxxx
> Cc: computer-go@xxxxxxxxxxxxxxxxx
> Subject: Re: [computer-go] Pattern Matcher
>
>
> I have seen benchmarks where some idiots do just memory allocations and
> deallocations where java is faster than C. Which is published on the
> website of Sun.
>
> However you can also write the software without stupid memory allocations
> and deallocations, then the C code is 3 times faster than the java code.
>
> Saying it's "just 30% slower" is not exactly true. It's 3 times slower.
>

Sorry, Vincent, absolutely not true for Go programming. A straight
translation of Goliath from C to Java lost about 30% in speed given the
right choice of JIT. And that was not because of allocation and
deallocations, as there are zero of that after initialisation.


_______________________________________________
computer-go mailing list
computer-go@xxxxxxxxxxxxxxxxx
http://www.computer-go.org/mailman/listinfo/computer-go/