Lester, On Wed, Dec 9, 2015 at 1:02 PM, Lester Caine <les...@lsces.co.uk> wrote:
> On 09/12/15 16:24, Rowan Collins wrote: > >> So as somebody already said, maybe your code or setup is really busted. > > > > Really busted, or spending all its time in a type of operation that ZE3 > > can't particularly optimize... > > But I'd like to understand why what is fairly simple PHP code is > apparently not working as some of you seem to expect. Much of the > original code goes back to PHP4 days and has been optimised and updated > over the years and re-factored a couple of times. It's doing the jobs > required and giving response times that clients are happy with in the > sub second on intranets. The only PHP7 fixes so far is a few __construct > changes from the original named constructor ... the rest of the code is > already e_strict clean. > This states nothing of how the code was architected and therefore cannot provide any realistic baseline as others have noted. In addition to this, your comparing apples to oranges. The speed increases in PHP itself do not always translate 100% to application performance. Without looking at execution performance on a function level and realizing what is actually taking the time this is a worthless conversation to be frank. > > So where should I be looking to work out why PHP7 seems little better > than PHP5. This code is ADOdb and Smarty based with templates which have > developed over 10+ years and we can switch on page caching for the > static material, but many sites are running with dynamic data such as > calling clients from queues and displaying dynamic information pages. > ADOdb and Smarty have not had MAJOR releases in several years. Smarty 3.1 was in 2011 while Smarty 3 was in 2010. ADOdb's last major release was in 2007. These are your implementation details and things that YOU are leveraging, these are not necessarily a standardized approach. Page caching changes things dramatically as now you're simply requiring things. If your spending time in query execution then thats why there is no significant gain. Overall, profile your code, look at the cachegrind output in the case of xdebug and then look at instruction time. Then you will have an idea where the time is being spent and can actually have a concrete discussion around performance and what is actually taking the processing time. Anything short of that, including this reply is a waste of time for everyone on this list. > > -- > Lester Caine - G8HFL > ----------------------------- > Contact - http://lsces.co.uk/wiki/?page=contact > L.S.Caine Electronic Services - http://lsces.co.uk > EnquirySolve - http://enquirysolve.com/ > Model Engineers Digital Workshop - http://medw.co.uk > Rainbow Digital Media - http://rainbowdigitalmedia.co.uk > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > >
