ISISComputingGroup / ISISComputingGroup/IBEX
DAE: Changing runstate performance
- Dominant language
- No language data
- Stars
- 6
- Forks
- 2
- Avg merge
- 16h 40m
- Merged PRs (30d)
- 2
Description
Discovered as part of https://github.com/ISISComputingGroup/IBEX/issues/4547 that performance of `g.begin`, `g.pause` etc. is much slower in IBEX than in SECI. This is an issue particularly when scanning as these commands are run many times as part of a typical scan, thus having a big impact on performance.
From Freddie's comment from the ticket above:
> The ibex begin does more than a seci begin, it resyncs run control and also restarts (and checks has restarted) the archive engine. These operations could be moved into separate DB monitoring logic and so run independently after a begin has started
Acceptance Criteria:
- The time it takes to execute `begin`, `pause` and `resume` from genie_python is comparable to the time it takes in OpenGENIE:
- around 3s for `begin`
- around 0.7s for `pause`
- around 0.15s for `resume`
- All necessary background processes for these commands are performed correctly.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.