Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.programming.threads > #5089 > unrolled thread

Disadvantages of Transactional memory

Started byHorizon68 <horizon@horizon.com>
First post2019-07-04 14:16 -0700
Last post2019-07-04 14:16 -0700
Articles 1 — 1 participant

Back to article view | Back to comp.programming.threads


Contents

  Disadvantages of Transactional memory Horizon68 <horizon@horizon.com> - 2019-07-04 14:16 -0700

#5089 — Disadvantages of Transactional memory

FromHorizon68 <horizon@horizon.com>
Date2019-07-04 14:16 -0700
SubjectDisadvantages of Transactional memory
Message-ID<qflqbe$huq$5@dont-email.me>
Hello...


Read the following paper about the disadvantages of Transactional memory:


"Hardware-only (HTM) suffers from two major impediments:
high implementation and verification costs lead to design
risks too large to justify on a niche programming model;
hardware capacity constraints lead to significant performance 
degradation when overflow occurs, and proposals for managing overflows 
(for example, signatures ) incur false positives that add
complexity to the programming model.

Therefore, from an industrial perspective, HTM designs have to provide 
more benefits for the cost, on a more diverse set of workloads (with 
varying transactional characteristics) for hardware designers to 
consider implementation."

etc.

"We observed that the TM programming model itself, whether implemented 
in hardware or software, introduces complexities that limit the expected
productivity gains, thus reducing the current incentive for migration to 
transactional programming, and the justification at present for anything 
more than a small amount of hardware support."


Read more here:

http://pages.cs.wisc.edu/~cain/pubs/cascaval_cacm08.pdf



Thank you,
Amine Moulay Ramdane.

[toc] | [standalone]


Back to top | Article view | comp.programming.threads


csiph-web