It's very likely that your development environment gets hitting those limits, no matter if you configured it for production under conf.d folder, or if you are using the default values. For example, if you're debugging, the debugger might add extra memory footprint, and it probably hit the execution timeout.
What I'm doing here is basically to disable those limits for development. This should make your dev life happier, out of the box.
For older Odoo versions, these limits were being ignored anyways, so it shouldn't harm.
In Odoo v12, the threaded mode (a.k.a.
--workers=0), which works best for development and unit testing, started processing some limits from the config.It's very likely that your development environment gets hitting those limits, no matter if you configured it for production under
conf.dfolder, or if you are using the default values. For example, if you're debugging, the debugger might add extra memory footprint, and it probably hit the execution timeout.What I'm doing here is basically to disable those limits for development. This should make your dev life happier, out of the box.
For older Odoo versions, these limits were being ignored anyways, so it shouldn't harm.