Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update documentation about non-deterministic diameter with multiple workers #942

Merged
merged 1 commit into from
Jun 14, 2024

Conversation

FedericoPonzi
Copy link
Contributor

Persist the learning from issue #883. Diameter is non-deterministic when the BFS is run with multiple workers.

When using multiple workers on a medium-small model, the reported <i>Diameter</i> might
differ across runs.
This is a limitation we accept to avoid putting additional synchronization that would limit
the scalability of the visit. For small models, use a single worker. For large models,
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Perhaps just "that would limit scalability"?

@@ -96,6 +101,8 @@ <h3><a name="model-mode">Model-checking mode</a></h3>
queue, so it does not produce any
<i>Diameter</i> or <i>Queue size</i>
statistics.
Additionally, <em>Depth-first</em> option doesn't currently
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The confusion typically comes from the fact that TLC does not plain depth-first but depth-first iterative deepening (DFID). We should consistently call it by its full name.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the insight! I've updated the paragraph.

@@ -30,6 +30,10 @@ ISpec == IM!Spec

TLC cannot handle natural numbers greater than 2<sup>31</sup> - 1.

When running the model checking in BFS mode with multiple workers on a medium-small model, the reported diameter might differ across runs.
This is a limitation we accept to avoid putting additional synchronization that would limit the scalability of the visit.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Perhaps just "that would limit scalability"?

@FedericoPonzi FedericoPonzi force-pushed the issue-883 branch 2 times, most recently from 2fe9752 to 5e840cd Compare June 12, 2024 16:10
Persist the learning from issue tlaplus#883. Diameter is
non-deterministic when the BFS is run with multiple workers.

Signed-off-by: Federico Ponzi <me@fponzi.me>
@Calvin-L Calvin-L merged commit 671a006 into tlaplus:master Jun 14, 2024
6 checks passed
@FedericoPonzi FedericoPonzi deleted the issue-883 branch June 30, 2024 21:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

3 participants