H! :D -- Clojure uses MVCC, which may help with this. http://en.wikipedia.org/wiki/Multiversion_concurrency_control
But as Hickey points out, no one really knows yet because there aren't enough high-core machines doing real work in the field. http://groups.google.com/group/clojure/msg/cd3e77afb75441d8 I put that second sentence in more as a joke than a Deep Insight; it's a reference to a silly song I like called "The Sweater Song": "If you want to destroy my sweater / Hold this thread as I walk away." Cheers, Carlos On Apr 13, 12:02 am, Baishampayan Ghose <b.gh...@ocricket.com> wrote: > Hi, > > This is an interesting article on the problems associated with > concurrency and some of the current solutions. > > http://www.facebook.com/notes/facebook-engineering/a-dismal-guide-to-... > > It mentions Clojure for a bit and says this about the general idea > behind STMs - > > "... STM has its own special problems, like how to perform those > commit/abort/retry cycles efficiently on thousands of threads. It's fun > to imagine pathological conflict scenarios in which long chains of > transactions unravel like a cheap sweater." > > Would anyone like to comment on how that affects the Clojure STM (if at > all)? > > Regards, > BG > > -- > Baishampayan Ghose <b.gh...@ocricket.com> -- 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 from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en
