Tim Mackey
Having access to performance data on our tasks would help us to optimize our tasks, especially when a) writing tasks for the task library, and b) writing storefront-interactive tasks that need quick response times.
Data I can see being useful:
  • Shopify API Usage
    - Is my task eating up my API rate limit? Could it be optimized by using GraphQL instead of REST/external liquid objects?
  • Mechanic Usage
    How long is my task taking to complete? Is my logic placing a heavy performance burden on Mechanic? Should I try to simplify that 5-layers-deep nested for-loop?