Hello Ron,
the first rule about optimizing is the 80-20 or 90-10 rule or whatever
you like more. Either way the idea is that the program spends more than
90% of it's run-time in less than 10% of it's functions. This is a very
general idea but nontheless has proven right since people program. On
the contray this rule means that you should spend 90% of your optimizing
power in those 10%. Much of it identifying these 10%. Now guess you were
finding all the small things you aim for, you as must as increase he 90%
that have little to non influence on the overall run-time efficiency.
Just in case anybody wanted to hear this :-)
best regards
marcus
Tuesday, March 14, 2006, 12:48:33 PM, you wrote:
> It's probably not measurable, but a lot of small improvements like these may
> be measurable. I don't know how often this situation occurs per request, but
> if it happens for all apache config flags and php.ini flags, it may be worth
> improving. If an improvement is not measurable per request (but is
> measurable as an isolated case), is that a reason not to do it? I don't
> think so. But I'm not the one to judge :) So I'll just leave this up to the
> big kahuna's, and I don't really feel like something this small justifies
> any big discussions.
> Ron
> "Edin Kadribasic" <[email protected]> schreef in bericht
> news:[email protected]...
>> Ron Korving wrote:
>>> Oh right, okay. For a moment I thought you were talking about a
>>> variable-length case insensitive string compare based on this principle
>>> :) Your macro seems like a good idea to me. The function I was talking
>>> about was an apache-flag checking function, not php.ini, but I guess this
>>> could just as well be applied for php.ini.
>>>
>>> Like I said, the speedup is about 5x, so I think it's worth it.
>>
>> The speedup of a single function might as well be 5x, but how many time is
>> it called and can the performance increase be measured in benchmark test
>> such as the that was posted by Rasmus?
>>
>> Edin
Best regards,
Marcus