Multi-threaded TLC Simulation Mode
See original GitHub issueCurrently, TLC does not take advantage of multiple threads when running in simulation mode (-simulate
). It would be desirable to have this. Presumably, each thread would start up a simulation run with a different seed, to increase total randomized coverage.
As a workaround, it is currently possible to start up multiple TLC processes (separate JVM instances) with different simulation seeds to achieve essentially the same effect.
Issue Analytics
- State:
- Created 6 years ago
- Comments:15 (14 by maintainers)
Top Results From Across the Web
Re: Multi-threaded TLC Simulation Mode - Mail Thread Index
I am trying to check a model with TLC using the following parameters (the specific spec isn't really important):. java tlc2.TLC -simulate -depth...
Read more >Running TLC in Distributed Mode - TLA+
Each slave computer can run multiple threads--the default is to run as many threads as it has processors (cores). TLC keeps fingerprints of...
Read more >Multithreaded Simulation Using For Each Subsystem
This example shows how to speed up execution of a model on multiple cores using a For Each subsystem in Rapid Accelerator simulation...
Read more >Current and Future Tools for Interactive TLA+
TLC's simulation mode makes print more useful. Enable it in the Toolbox's “TLC Options” pane and set max traces to 1.
Read more >Specifying and Verifying Systems With TLA+ - Leslie Lamport
simulations of even infinite-state specifications. TLC can be used to check safety and liveness ... TLC can run in multi-threaded mode to make...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@will62794 Today I was sufficiently annoyed by the slow tests myself and decided to give it a quick stab. 12h later I arrived at f9f35f35b74289d85b2f75b09f37703281f984de which halves the test suite’s execution time from ~12min to ~6min on my machine.
605fb0f9c0a77ce3572955eda94c5ed1909531ce
Just for LiveCheck1 because (I believe) LiveCheck is thread-safe.