End-to-end profiling
It would be nice to benchmark the full execution time of the workflow from the end of the scan to the plotting of the result.
This should be done both on the blissoda side, and the workflow side. I expect to know about:
- blissoda overheads
- slurm overheads, submission. allocation, load of the module
- ewoks overheads, worker submit (should be small)
- workflow execution, reading, reconstruction, writing
- gathering of the result and plot in flint