Posted by Colin McKinnon on 03/30/07 23:21

Hi all,

I am currently working on a project which involves using a lot of code on
each page. I'm currently refactoring with a view to performance and have
discovered that when my app starts to include the class definitions it
needs, the memory gets eaten up *very* rapidly - indeed, typically, the
memory usage is TEN TIMES the size the class file occupied on the disk -
note this memory usage is only as a result of require_once() not objects
are instantiated, no code within the files has been run at this point.

(there are some hard stats below)

Has anybody else noticed this? Thought it a bit excessive? Found a more
efficient way of building the code (should I consider 'compiling' the
include files into a single one?). Unfortunately all the code is needed so
while the larger files do have more than one class definition there doesn't
seem to be much to be saved by using the autoloader.

TIA,

file mem used by require size on disk ratio
form.inc.php 704912 81766 8.62
widgets.inc.php 738800 57368 12.88
linked.inc.php 80920 7286 11.11
rawwidget.inc.php 74864 7497 9.99
iterator.inc.php 123536 11451 10.79

C.

[Back to original message]