On OSX (.availableProcessors (Runtime/getRuntime)) returns 2 in my case.
I've also run into the following thread:
https://groups.google.com/forum/#!topic/clojure/AtA-0LKYe9A
There are two other implementations of CPU bound pmap: pmapall and
pmap-pool. The latter one (by j-g-faustus) actually sol
Thanks all for advise and sorry for the double post.
Will check this out tonight and get back.
Cheers,
kuba
On Wednesday, May 1, 2013 11:09:05 AM UTC-7, kuba roth wrote:
>
> Hi there,
>
> I'm currently testing a map/pmap performance and run into weird
> behavior in Clojure running on a OSX (co
You can substitute (iterate inc 0) for (range) to get an unchunked version
of (range), BTW.
On Wed, May 1, 2013 at 2:56 PM, Marshall Bockrath-Vandegrift <
llas...@gmail.com> wrote:
> kuba roth writes:
>
> > I've got more examples for OSX which clearly shows that as soon as the
> > number of tas
kuba roth writes:
> I've got more examples for OSX which clearly shows that as soon as the
> number of tasks exceeds number of cores pmap performance suffers. It
> seems to me like there is no blocking taking place on threads and all
> the tasks are started at the same time.
There’s a still-open
Hi there,
I'm currently testing a map/pmap performance and run into weird
behavior in Clojure running on a OSX (compered to Linux).
Running a 'slow' (processor intensive pmap function on OSX suffers
from very poor performance whereas the same function on Linux runs
just fine.
At the first glance l
