[Solar-talk] Performance ideas

[Rodrigo Moraes]

On 10/16/07, Ian Szewczyk wrote:
> I agree about the excessive use file_exists/class_exists when it comes
> to loading classes.  The fact that every path in the include path is
> scanned makes it a little worse, and then multiply that when used in
> conjunction with the file and class stacks. I mentioned a while back
> that caching the absolute paths might be a good idea for production
> environments, but its hard to wiggle that in on your own because there
> are dependencies inside the arch class, and the usage of the stack
> classes by the core api is pretty tightly woven in as well.

Just wondering... how many Solar classes could be mapped statically to
absolute paths, I mean, do not depend on Solar_Class_Stack? Maybe a
hook to break file_exists/class_exists for mapped classes could be
added, so that you could map *all* or just some classes, if you
wanted... Anybody tried something like this?

The class stack is a powerful tool... I'd not think to change it;
however I tend to use many stack tricks, everywhere.

-- rodrigo