2009/9/17 z5h bolusm...@gmail.com:
Specifically some problems encountered in Clojure's STM and bytecode
generation.
http://www.azulsystems.com/events/javaone_2009/session/2009_J1_JVMLang.pdf
(Slide's 8 and 20-21)
I suppose you mean slide 9 rather than 8:
Clojure - “almost close”
* Good:
Also the slide 21 should worth an answer: a benchmark of STM with more CPU
gives Performance died – choked in the STM
On Fri, Sep 18, 2009 at 9:22 AM, Michael Wood esiot...@gmail.com wrote:
2009/9/17 z5h bolusm...@gmail.com:
Specifically some problems encountered in Clojure's STM and
On Thu, Sep 17, 2009 at 5:22 PM, John Harrop jharrop...@gmail.com wrote:
On Thu, Sep 17, 2009 at 3:06 PM, Mark Volkmann r.mark.volkm...@gmail.com
wrote:
On Thu, Sep 17, 2009 at 1:43 PM, z5h bolusm...@gmail.com wrote:
Specifically some problems encountered in Clojure's STM and bytecode
Click answers that himself: Clojure usage failure.
The particular scenario he is demonstrating is known and has been brought up
before. Also it's probably only reproduceable when you have a truly large
number of cores (like a 600 way Azul box). In anycase Rich Hickey does not
advise against locks
On Fri, Sep 18, 2009 at 8:34 AM, Mark Volkmann r.mark.volkm...@gmail.comwrote:
On Thu, Sep 17, 2009 at 5:22 PM, John Harrop jharrop...@gmail.com wrote:
On Thu, Sep 17, 2009 at 3:06 PM, Mark Volkmann
r.mark.volkm...@gmail.com
wrote:
On Thu, Sep 17, 2009 at 1:43 PM, z5h
Specifically some problems encountered in Clojure's STM and bytecode
generation.
http://www.azulsystems.com/events/javaone_2009/session/2009_J1_JVMLang.pdf
(Slide's 8 and 20-21)
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the
On Thu, Sep 17, 2009 at 1:43 PM, z5h bolusm...@gmail.com wrote:
Specifically some problems encountered in Clojure's STM and bytecode
generation.
http://www.azulsystems.com/events/javaone_2009/session/2009_J1_JVMLang.pdf
(Slide's 8 and 20-21)
Slide 20 - Should say Nothing mutable by default
