Improve task testing performance #5488
Description
What should we do?
Depending on the usage scenario, task testing currently has a response time of around 6 seconds, which I regard as slow. The more I have to wait, the less I'm inclined to use the tool.
(Of course, we'd want to validate this claim, and carefully monitor user feedback).
I'd like us to investigate
- (1) what makes it slow
- (2) In which scenarios
- (3) what pragmatic ways we see to improve the perceived performance ("what features would we need to make it faster")
Why should we do it?
Slow task testing can be an adoption blocker.
Improvement ideas
- Fail early: In the context of task testing you don't want to execute a job worker with retries, but get immediate feedback on what is wrong. This improves reactivity, display of results.
- Decrease delay for primary to secondary storage export: In DEV setups export intervals could be shortened. This improves reactivity, display of results (ref)
Related to #5487