Creating this issue in response to performance issues observed when the mjml app was included in installed apps.
We observed a slowdown of several seconds for app starts, restarts/reloads, and test runs, due to the check_mjml_command() invocation in MJMLConfig.ready(). As best as we can tell there is currently no way to avoid this performance hit on every app start/test run/reload.
Once a server has been configured in a stable environment, the administrator should have some level of control over whether this command is invoked every time a django process starts.
Our suggestion is to include a simple boolean setting (MJML_SKIP_CMD_CHECK?) which will allow an administrator to have fine-grained control over this startup behavior.
Creating this issue in response to performance issues observed when the
mjml
app was included in installed apps.We observed a slowdown of several seconds for app starts, restarts/reloads, and test runs, due to the
check_mjml_command()
invocation inMJMLConfig.ready()
. As best as we can tell there is currently no way to avoid this performance hit on every app start/test run/reload.Once a server has been configured in a stable environment, the administrator should have some level of control over whether this command is invoked every time a django process starts.
Our suggestion is to include a simple boolean setting (
MJML_SKIP_CMD_CHECK
?) which will allow an administrator to have fine-grained control over this startup behavior.(PS: Thanks for creating this great library!)