Bug #25

Scm consistency check takes too long

Added by Grégoire Sutre over 6 years ago. Updated over 5 years ago.

Status:New Start date:
Priority:High Due date:
Assignee:Tristan Le Gall % Done:

0%

Category:-
Target version:1.x

Description

On large examples, the scm consistency check takes a very long time. The attached scripts produce scm models that are simple (no actions) but large.

  • flat.scm.sh size: a single automaton with size locations and size transitions.
  • product.scm.sh size: a product of size automata, each consisting of 2 locations and 2 transitions.

The times in the table below have been obtained with the following commands (see attached files) :

sh flat.scm.sh    <size> | mcscm.native -statistics
sh product.scm.sh <size> | mcscm.native -statistics

On these examples (which do not have bad states), 95% of the total running time is taken by the scm consistency check. The table also contains an entry for the peterson_3.scm example, where 90% of the total running time is taken by the scm consistency check.

Size Locations Transitions Consistency Check
Flat 10000 10000 10000 4.12 s
20000 20000 20000 21.45 s
30000 30000 30000 48.43 s
Product 11 2048 22528 2.24 s
12 4096 49152 15.14 s
13 8192 106496 80.88 s
Peterson 3 10648 56628 37.80 s

flat.scm.sh (247 Bytes) Grégoire Sutre, 07/22/2010 03:09 pm

product.scm.sh (228 Bytes) Grégoire Sutre, 07/22/2010 03:09 pm


Related issues

related to McScM - Feature #26: Optimize scm cartesian product (or avoid it) New

History

Updated by Grégoire Sutre almost 6 years ago

  • Target version set to 1.x
  • Start date deleted (07/22/2010)

Updated by Tristan Le Gall over 5 years ago

  • Assignee set to Tristan Le Gall

Also available in: Atom PDF