Allow instrumentation of migration steps to check for slowdowns/memory leaks

kaliop-uk / ezmigrationbundle

This bundle makes it easy to handle eZPlatform / eZPublish5 content upgrades/migrations

GNU General Public License v2.0

53 stars 81 forks source link

Allow instrumentation of migration steps to check for slowdowns/memory leaks #200

Closed gggeek closed 3 years ago

gggeek commented 5 years ago

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.

it is known that the ez4 kernel has in-memory caching of content objects, which needs periodic purging when running large jobs
eZPlatform 2.5 and later also have an in-memory cache, albeit that one is size-limited by design

gggeek commented 5 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

gggeek commented 3 years ago

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