More and more developers report problems with memory usage in development mode, when an eZ page is run uncached and e.g. fetches a few hundred contents or more.

While proper configuration of SPI cache, php memory limit and a few other tunables does allow to work around this problem, it still poses a hurdle to development:

• some devs use VMs which can not allow 2 or 3 GB of ram for php
• some devs will take a wrong path anyway and waste time tweaking their code optimizing it for dev mode instead of prod mode

In short: eZ should be less memory-hungry by defult in dev mode, or at least be much more friendly in explaining where the memory is used and how to fix memory limitations