Introduction page for ZIO STM #4957

khajavi · 2021-04-13T11:26:30Z

No description provided.

khajavi · 2021-04-14T08:02:59Z

Hey @jdegoes
It's ready to be reviewed.

mijicd

Just one small remark which might be treated as a nitpick. Other than that, great work!

P. S. I'd still wait for a sign off by some of the native speakers 😄

mijicd · 2021-04-15T22:36:14Z

docs/datatypes/stm/index.md

+
+2. **Virtual Execution** — The runtime starts speculating the execution of transactions on every read and write operation. It has two internal logs;  the read and the write log. On the read log, it saves the version of all variables it reads during the intermediate steps, and on the write log, it saves the intermediate result of the transaction. It doesn't change the shared state on the main memory. Anything that is inside an atomic block is not executed immediately, it's executed in the virtual world, just by putting stuff in the internal log, not in the main memory. In this particular model, we guarantee that all computations are isolated from one another.
+
+3. **Commit Phase (Real Execution)** — When it came to the end of the transaction the runtime system should check everything it has read. It should make sure that it saw a consistent state of the universe and if it had, then it atomically commits. As the STM is optimistic, it assumes that in the middle of a transaction the chance of interfering with the shared state by other fibers is very rare. But it must ready itself for the worst cases. It should validate its assumption in the final stage. It checks whether the transactional variables involved were modified by any other threads or not. If its assumption got invalidated in the meanwhile of the transaction, it should abandon the transaction and retry it again. It jumps to the start of the transaction with the original and default values and tries again until it succeeds; This is necessary to resolve conflicts. Otherwise, if there was no conflict, it commits the final value atomically to the memory and succeeds. From point of view of other fibers, all values in memory exchanging in one blink of an eye. It's all atomic.


I would emphasize "the obvious" here, i. e. read rather than writes, "short" transactions rather than the "long" ones. Perhaps it also makes sense stating that we will try to prevent retry storms with a bit crude heuristic - after a certain number of retries is reached, lock & complete.

khajavi added 4 commits April 13, 2021 15:54

write an introduction page for zio stm.

4a35968

move data type introduction from stm page to introduction page.

7743275

remove unrelated documentation from stm page.

42e0db4

split big paragraphs.

864e737

mijicd approved these changes Apr 15, 2021

View reviewed changes

jdegoes approved these changes Apr 19, 2021

View reviewed changes

jdegoes merged commit 7c6d984 into zio:master Apr 19, 2021

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Introduction page for ZIO STM #4957

Introduction page for ZIO STM #4957

khajavi commented Apr 13, 2021

khajavi commented Apr 14, 2021

mijicd left a comment

mijicd Apr 15, 2021


		2. Virtual Execution — The runtime starts speculating the execution of transactions on every read and write operation. It has two internal logs; the read and the write log. On the read log, it saves the version of all variables it reads during the intermediate steps, and on the write log, it saves the intermediate result of the transaction. It doesn't change the shared state on the main memory. Anything that is inside an atomic block is not executed immediately, it's executed in the virtual world, just by putting stuff in the internal log, not in the main memory. In this particular model, we guarantee that all computations are isolated from one another.

		3. Commit Phase (Real Execution) — When it came to the end of the transaction the runtime system should check everything it has read. It should make sure that it saw a consistent state of the universe and if it had, then it atomically commits. As the STM is optimistic, it assumes that in the middle of a transaction the chance of interfering with the shared state by other fibers is very rare. But it must ready itself for the worst cases. It should validate its assumption in the final stage. It checks whether the transactional variables involved were modified by any other threads or not. If its assumption got invalidated in the meanwhile of the transaction, it should abandon the transaction and retry it again. It jumps to the start of the transaction with the original and default values and tries again until it succeeds; This is necessary to resolve conflicts. Otherwise, if there was no conflict, it commits the final value atomically to the memory and succeeds. From point of view of other fibers, all values in memory exchanging in one blink of an eye. It's all atomic.

Introduction page for ZIO STM #4957

Introduction page for ZIO STM #4957

Conversation

khajavi commented Apr 13, 2021

khajavi commented Apr 14, 2021

mijicd left a comment

Choose a reason for hiding this comment

mijicd Apr 15, 2021

Choose a reason for hiding this comment