Re: ForkJoin updates

Here's a new blog post describing the effect the improved fork-join pool has had on Akka actors: http://letitcrash.com/post/17607272336/scalability-of-fork-join-pool -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email

Re: ForkJoin updates

This is exactly what I meant. :) -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe fro

Re: ForkJoin updates

I think the suggestion from the OP is to change the computational executor pool in Agent from an Executors to a ForkJoinPool to get better scalability. Indeed, the work Doug has been in doing is in response to many libs using fork/join as an alternative to Executors to schedule lightweight computa

Re: ForkJoin updates

There was some excellent work on ForkJoin in Clojure by David Liebke and others last year, but it never made it into the main Clojure branch. It's waiting for someone else to finish it. Search the wiki and mailing list for notes. -S -- You received this message because you are subscribed to t

ForkJoin updates

This has been posted to the concurrency-interest mailing list. Apparently there have been some nice improvements to ForkJoin: ...This also greatly improves throughput when all tasks are async and submitted to the pool