8 ms·
Ah, the promise of Clojure and easy parallel programming is near at hand. At what number of cores, does Clojure become a lay-up choice over other hard to paral
by jgalt212 12y ago
Ah, the promise of Clojure and easy parallel programming is near at hand. At what number of cores, does Clojure become a lay-up choice over other hard to parallel languages? Anyone care to opine?
- signa11 12y ago> Ah, the promise of Clojure and easy parallel programming is near at hand. clojure, golang and before all that erlang as well (and myriads of libraries e.g. cilk etc). dearth of parallel languages have never really been the issue, imho. <the 'opine' part> it's how to move existing applications to new h/w, with the caveat that doing a flat out re-write is almost out of question. hoping that there will eventually be compiler that can just parallelize your application code, is just a pipe dream, imho.
- ansgri 12y agoI often find (in my own code as well) that nobody ever remembers OpenMP. It has some overhead, but it's not that big even without fixed thread count tuning (with which it nearly vanishes). Not automatic, but damn close.
- ebiester 12y agoWhat is the problem you're trying to solve? If your problem is "I have a lot of requests from a web server that are quickly dispatched", then parallel programming doesn't get you anything. The problems where number of cores matter are already looking at parallel programming solutions because they're running the problems on multiple machines, right? NOW, for a new desktop application that would benefit from parallel programming, it becomes interesting. Perhaps the startup time of the JVM doesn't even matter anymore. :)
- jgalt212 12y ago> If your problem is "I have a lot of requests from a web server that are quickly dispatched", then parallel programming doesn't get you anything. why not? If a page render has 10 independent processes that must be completed before data can be returned to client, doesn't the pmap function give an approx 10X speed-up? Or are you talking in the aggregate where each request is being handle in its own thread, and then the page render speed is really just I/O bound. But even in that case if the web server is doing some heavy computation (wolfram alpha, for example) easy parallelization of a request can make the web a more effective compute engine.