Re: Xdebug: what do the different execution times mean?

From: Date: Fri, 04 Jul 2003 18:25:37 +0000
Subject: Re: Xdebug: what do the different execution times mean?
References: 1 2 3  Groups: php.pear.general 
Request: Send a blank email to pear-general+get-6484@lists.php.net to get a copy of this message
On Fri, 4 Jul 2003, Jeroen Houben wrote: > Jeroen Houben wrote: > > > Hi all, > > Can anyone tell me what exactly the difference is between these things? > > > > Opcode Compiling: 0.0006799698 > > Function Execution: 0.0021259584 > > Ambient Code Execution: 0.0019040309 > > Total Execution: 0.0040299892 > > > > I'm trying to cache a certain group of method calls, which take a long > > time. > > (it's a recursive tree setup to generate a collapsable JS menu) > > > > Problem is that using the cache I gain lots of speed in the Ambient > > Code Execution, but it's only just moved to Opcode Compiling. But I > > don't really know the difference between the execution times.. > > > > I'm guessing I can fix that using APC, but I'm no speed expert. > > Wow APC got rid of almost all the Opcode compile time. APC and > Cache_Lite combined work really well. I would still like to know the > difference bewteen Function Execution and Ambient Code Execution. Can > anyone shed some light on this? It's the difference between the total execution time, and the function execution time; in other words: the time the engine is doing arbitrary stuff NOT related to a function call, ie: walking through the op array, checking method call visibility etc... Derick -- ------------------------------------------------------------------------- Derick Rethans http://derickrethans.nl/ JDI Media Solutions http://www.jdimedia.nl/ International PHP Magazine http://www.php-mag.net/ -------------------------------------------------------------------------

« previous php.pear.general (#6484) next »