Closed gggeek closed 3 years ago
Note: this is already possible via adding custom event listeners for migration steps. What we can do is probably add some such event listener, that we keep disabled by default and make available for activation via a parameter
Implemented as part of the existing TracingStepExecutedListener. In order to activate tracing of time and memory taken per step, just run migrations with '-vv'. Will be in 5.13
Some users have reported that long migrations (ie. one with loops and many steps) "slow down over time". It might be worth adding timing points and memory-consumption checks in order to troubleshoot any causes for such problems. Eg.