Processing time for scan creation: large arrays as input for PathOptimizer #754
Description
Provide a brief description of the bug.
If Python get stuck in creation of the scan in longer operations, we are locked and delay the execution of the scan. This can be misinterpreted as a bug of the scan which the user interrupts. For sub-sequent scan submissions, the scan-server will print a warning that a worker is still busy.
One example for this is the usage of the PathOptimizer, which depending on the input parameters will be called for large arrays. This may result in significant overhead in the creation of the scan. At the very least, we should implement a warning for such inputs in case of the PathOptimizer. For the PathOptimizer, we may in addition implement cached optimizations.
Describe what you expected to happen and what actually happened.
No response
Outline the steps that lead to the bug's occurrence. Be specific and provide a clear sequence of actions.
No response
bec_widgets version
No response
bec core version
No response
Any extra info / data? e.g. log output...
No response
Related issues
No response