On 05/15/2010 02:53 AM, Patrick Wright wrote:
> For more details about Microsoft's work on STM, and the many, many
> problems they had to address, see Joe Duffy's blog on the topic
> http://www.bluebytesoftware.com/blog/2010/01/03/ABriefRetrospectiveOnTransactionalMemory.aspx
>
I have just about
For more details about Microsoft's work on STM, and the many, many
problems they had to address, see Joe Duffy's blog on the topic
http://www.bluebytesoftware.com/blog/2010/01/03/ABriefRetrospectiveOnTransactionalMemory.aspx
--
You received this message because you are subscribed to the Google
Gr
The problem with STM is that it adds significant overheads to modification
costs. In a "classic" imperative programming language like Java or C#,
stores to variables compile down to simple memory writes- very cheap. An
STM memory write, by contrast, is 10x or 100x more expensive (depending upon
p
Hi people!
A 2008 paper, I just received today via twitter
*Software transactional memory**: why is it only a research toy?*
http://portal.acm.org/citation.cfm?id=1400228&coll=ACM&dl=ACM&CFID=90273999&CFTOKEN=67127907&ret=1#Fulltext
Angel "Java" Lopez
http://www.ajlopez.com
http://twitter.com/aj
Not directly related to Clojure but I thought this would be of interest to
folks:
http://www.infoq.com/news/2010/05/STM-Dropped
http://www.reddit.com/r/programming/comments/c4367/microsofts_experiments_with_software/
--
You received this message because you are subscribed to the Google
Groups "C
