He talks about simple things actually. When you have any sort of immutable data structure and you want to change it from multiple threads you just must have a mutable reference which points to the current version of that data structure. Now, updates to that mutable reference are fundamentally serial. Whatever synchronization strategy you chose been that optimistic updates (atom) or queuing (agent) or locks you inevitably will have a contention on a large number of threads. When you will run on that you will also have hundred ways to solve a problem.
There is nothing magical about persistent data structures on multi-core machines :) четверг, 13 марта 2014 г., 20:58:54 UTC+4 пользователь Andy C написал: > > Hi, > > So the other day I came across this > presentation:http://www.infoq.com/presentations/top-10-performance-myths > > The guy seems to be smart and know what he talks about however when at > 0:22:35 he touches on performance (or lack of thereof) of persistent data > structures on multi-core machines I feel puzzled. > > He seems to have a point but really does not back it with any details. > There is also a claim that STM does not cooperate well with GC. Is it true? > > Thanks, > Andy > > > -- 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 --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.