Thats a unique idea.You should consider the following idea to enhance your idea so that it would impact uniquely:   investigate feedback-directed dynamic selection beten different implementations of atomic blocks.  initially execute atomic blocks using STM with optimistic concurrency control. At runtime,  identify “hot” variables that cause large numbers of transactions to abort. For these variables  selectively switch to using pessimistic concurrency control, in the hope of deferring transactions until they will be able to run to completion. This trades off a reduction in single-threaded speed (since pessimistic concurrency control is not as streamlined as our optimistic implementation), against a reduced amount of wasted work in aborted transactions.  describe our implementation in the Haskell programming language, and examine its performance with a range of micro-benchmarks and larger programs.  show that our technique is effective at reducing the amount of wasted work, but that for current workloads there is often not enough wasted work for an overall improvement to be possible. As  demonstrate, our technique is not appropriate for some workloads: the extra work introduced by lock-induced deadlock is greater than the wasted work saved from aborted transactions. For other workloads,  show that using mutual exclusion locks for “hot” variables could be preferable to multi-reader locks because mutual exclusion avoids deadlocks caused by concurrent attempts to upgrade to write access.
['Nehir Sonmez', 'Tim Harris', 'Adrián Cristal', 'Osman S. Unsal', 'Mateo Valero']
I am writing a research paper on a idea Taking the heat off transactions: Dynamic selection of pessimistic concurrency control
[{"from": "human", "value": "I am writing a research paper on a idea Taking the heat off transactions: Dynamic selection of pessimistic concurrency control"}, {"from": "gpt", "value": "Thats a unique idea.You should consider the following idea to enhance your idea so that it would impact uniquely:   investigate feedback-directed dynamic selection beten different implementations of atomic blocks.  initially execute atomic blocks using STM with optimistic concurrency control. At runtime,  identify \u201chot\u201d variables that cause large numbers of transactions to abort. For these variables  selectively switch to using pessimistic concurrency control, in the hope of deferring transactions until they will be able to run to completion. This trades off a reduction in single-threaded speed (since pessimistic concurrency control is not as streamlined as our optimistic implementation), against a reduced amount of wasted work in aborted transactions.  describe our implementation in the Haskell programming language, and examine its performance with a range of micro-benchmarks and larger programs.  show that our technique is effective at reducing the amount of wasted work, but that for current workloads there is often not enough wasted work for an overall improvement to be possible. As  demonstrate, our technique is not appropriate for some workloads: the extra work introduced by lock-induced deadlock is greater than the wasted work saved from aborted transactions. For other workloads,  show that using mutual exclusion locks for \u201chot\u201d variables could be preferable to multi-reader locks because mutual exclusion avoids deadlocks caused by concurrent attempts to upgrade to write access."}]