Algorithm Profiler #227
Description
Paint Point? Please describe.
When I'm building an algorithm, I may not have a clear understanding of what the runtime resource requirements are. We can spend time working to understand exactly what the memory footprint is or the CPU needs are, but it would be nice to see what the real consumption was following execution.
Desired Solution
It would be nice to utilize the docker stats feature following the execution to provide a break-down of what the resources max / avg resource utilization is. This feature could then be used provide real values for the seed resources block.