On Dec 7, 2012, at 5:25 PM, Lee Spector wrote:
>
> Another strange observation is that we can run multiple instances of the test
> on the same machine and (up to some limit, presumably) they don't seem to
> slow each other down, even though just one instance of the test appears to be
> maxing
Thanks Andy.
My applications definitely allocate a lot of memory, which is reflected in all
of that consing in the test I was using. It'd be hard to do what we do in any
other way. I can see how a test using a Java mutable array would help to
diagnose the problem, but if that IS the problem th
Lee:
I'll just give a brief description right now, but one thing I've found in the
past on a 2-core machine that was achieving much less than 2x speedup was
memory bandwidth being the limiting factor.
Not all Clojure code allocates memory, but a lot does. If the hardware in a
system can write
I've been running compute intensive (multi-day), highly parallelizable Clojure
processes on high-core-count machines and blithely assuming that since I saw
near maximal CPU utilization in "top" and the like that I was probably getting
good speedups.
But a colleague recently did some tests and
101 - 104 of 104 matches
Mail list logo
