Workflow specification is parsed too many times
Bug #1541786 reported by
Thomas Herve
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mistral |
Fix Released
|
Medium
|
Thomas Herve |
Bug Description
During creation and execution, a single workflow can be parsed numerous times, most of the time uselessly. As it's fairly expensive, we should at least try to pass the parsed specification when we have it, instead of reparsing again.
Changed in mistral: | |
assignee: | nobody → Thomas Herve (therve) |
Changed in mistral: | |
status: | New → In Progress |
Changed in mistral: | |
importance: | Undecided → Medium |
milestone: | none → mitaka-3 |
Changed in mistral: | |
milestone: | mitaka-3 → mitaka-rc1 |
Changed in mistral: | |
milestone: | mitaka-rc1 → 2.0.0 |
To post a comment you must log in.
Reviewed: https:/ /review. openstack. org/275372 /git.openstack. org/cgit/ openstack/ mistral/ commit/ ?id=65a84b469a3 49aa313c22eac27 ecb8668a795623
Committed: https:/
Submitter: Jenkins
Branch: master
commit 65a84b469a349aa 313c22eac27ecb8 668a795623
Author: Thomas Herve <email address hidden>
Date: Tue Feb 2 18:31:37 2016 +0100
Reduce spec parsing in workflow lifecycle
During workflow creation and execution, its specification is parsed
multiple times uselessly. This reduces the load by simply passing around
the specification when it's available.
Change-Id: I5babdbf8e9bc0c f7f69cf724bc7f6 b0b270d1667
Closes-Bug: #1541786