#183: Check variable referencing, overwriting, memory use in Renderers
----------------------+-----------------------------------------------------
Reporter: david | Owner: dominik
Type: task | Status: closed
Priority: normal | Milestone: 1.0
Component: renderer | Version:
Severity: critical | Resolution: fixed
Keywords: | Has_patch: 0
----------------------+-----------------------------------------------------
Changes (by impl):
* status: new => closed
* has_patch: => 0
* resolution: => fixed
Comment:
This bug has a lot to do with the previous execution flow of Agavi.
Profiling the sample app, I observed a net change of 20K from
PhpRenderer::initialize() to the end of the render process, with peak
memory usage about 80K higher than at the beginning of ::initalize(). This
made use of multiple routing ::gen() calls, translation, and multiple
slots/layers, so I think we can safely say that either we or PHP are
taking care of memory usage fine here.
Across layers, each template call seems to also indicate a net change of
about 20K of memory, so there's no problem with decoration either, as the
original description suggests.
Net memory usage for a development mode (i.e., requiring compilation of
all config files) script using translation/localization, logging, and
other fun features: 11222K. Not bad.
Resolving as fixed due to our new execution flow model.
--
Ticket URL: <http://trac.agavi.org/ticket/183#comment:3>
Agavi <http://www.agavi.org/>
An MVC Framework for PHP5
_______________________________________________
Agavi Tickets Mailing List
[email protected]
http://lists.agavi.org/mailman/listinfo/tickets
