[Solar-talk] Namespacing with concrete class functionality (was: Re: Proposal: Remove namespace to Solar::loadClass()/factory())

Rodrigo Moraes rodrigo.moraes at gmail.com
Wed Nov 8 10:23:43 PST 2006


On 11/8/06, Travis Swicegood wrote:
>  These are all with a namespaces array of
> Solar, Domain51.
>
> Using the simplest form - loading a single class, it looks like there's
> a 5% hit in performance.  Using the bookmarks app, it looks like there
> was a 13% hit.  This just proves foreach() hurts anyway you shake it.
> I'm try some tweaks and see if I can get it better performance out of
> this.  If I can keep both under 5%, I'd be happy.

5% would not be bad. The real damage seems to happen when your primary
namespace doesn't have most of the classes that will be needed in a
real app. Then Solar will try to find many of the classes more than
once. Since adding precedence to a Vendor is one of the main reasons
to have namespaces, I think you should benchmark it using ('Domain51',
'Solar') for the namespaces array.

I didn't knew about ApacheBench, it's nice to know, will try it when I
need a benchmark. :-)

thanks,
rodrigo


More information about the solar-talk mailing list