Feature #10852
closed
Support parallel execution of Weaver
Added by Evgeny Novikov over 3 years ago.
Updated over 3 years ago.
Category:
Tasks generation
Description
Weaver instruments original source files and models sequentially that is pretty well for the production mode and when there are many verification tasks that are generated and solved in parallel. In the development mode or when there is the only verification task this is very inefficient. Indeed, Weaver can consume most of wall time at least for generation of verification tasks. It would be great to support parallel execution of Weaver and to have a separate option that will allow to specify the number of parallel workers for Weaver when starting a verification job decision.
- Status changed from New to Resolved
- Target version changed from 3.3 to 3.2
I did this in branch parallel-weaver. Let's see on CI results since it is a quite crucial improvement.
CI helped to reveal data races that I fixed in the same branch. Let's wait for new results.
- Status changed from Resolved to Closed
Tests passed, so, I merged the branch to master in e280b0df5. Existing configurations for job decisions will not work unless you will specify the number of parallel workers for "Weaving". By default in the development mode there are will be quite many Weaver workers (0.5, i.e. a half of CPU cores).
- Status changed from Closed to Open
CI reported a data race one more time. It turned out that I fixed it incorrectly last time. Unlike another data race, this one happens extremely seldom, but nevertheless it is crucial.
- Status changed from Open to Resolved
I fixed the data race in branch fix-data-race-weaver. Let's wait for CI results.
- Status changed from Resolved to Closed
Tests passed, so, I merged the branch to master in 9178752a8.
Also available in: Atom
PDF