15 Sep
2013
15 Sep
'13
1:15 p.m.
Hello! As far as I understand, pypy-stm reports only conflicts, but not transactions that turn inevitable. But if transaction turns inevitable, it means that other transactions can not proceed. So it is hard to debug loss of parallelization when some transactions turn inevitable but other transactions do not conflict - the program is just silently slow. Is this correct? Are there any plans on giving some hooks for this case, or stacktraces similar to aborting transactions? Or maybe there is some other method?