On 3/4/2011 10:03 AM, Barton Willis wrote:
>
> For the testsuite (using a Core 2 6400 (2.13 GHz) and 2 GB RAM), CCL is
> about 30% slower
> than GCL. Likely the testsuite is a poor speed benchmark.
I think that using profiling tools one could try to figure out what is
taking the bulk of
the time. Perhaps it is doing a relatively large percentage of input
and output
compared to computing. My benchmarks had essentially no I/O.
I ran my tests on a 3 GHz Pentium D with 3GB of RAM
running Windows XP
The profiling tools for CCL look very difficult to use -- see
http://ccl.clozure.com/ccl-documentation.html#Profiling
and appear to be available only for Linux and Mac, not windows.
also, in response to the question by Robert Dodier on 3/3 -- I found
this statement--
"32-bit x86 versions of Clozure CL depend on the presence of the SSE2
instruction set extensions."
See
http://trac.clozure.com/ccl/wiki/SystemRequirements
so for some people with older computers this would definitely be a problem.
I found no mention of a workaround.
And incidentally, the use of SSE2 instructions should give CCL a boost
over GCL;
if somehow CCL could be compiled without SSE2 it might be much more than
3X slower on the tests I used.
Just trying to keep track of the issues.