note 100137 added to control-structures.declare
| From: | Anonymous at osu1 dot php dot net | Date: | Mon, 27 Sep 2010 21:10:48 +0000 |
| Subject: | note 100137 added to control-structures.declare | ||
| Groups: | php.notes | ||
| Request: | Send a blank email to php-notes+get-172748@lists.php.net to get a copy of this message | ||
It's amazing how many people didn't grasp the concept here. Note the wording in the
documentation. It states that the tick handler is called every n native execution cycles. That means
native instructions, not including system calls (i'm guessing). This can give you a very good
idea if you need to optimize a particular part of your script, since you can measure quite
effectively how many native instructions are in your actual code.
A good profiler would take that into account, and force you, the developer, to include calls to the
profiler as you're entering and leaving every function. That way you'd be able to keep an
eye on how many cycles it took each function to complete. Independent of time.
That is extremely powerful, and not to be underestimated. A good solution would allow aggregate
stats, so the total time in a function would be counted, including inside called functions.
----
Server IP: 212.150.176.151
Probable Submitter: 77.125.96.215
----
Manual Page -- http://www.php.net/manual/en/control-structures.declare.php
Edit -- https://master.php.net/note/edit/100137
Del: integrated -- https://master.php.net/note/delete/100137/integrated
Del: useless -- https://master.php.net/note/delete/100137/useless
Del: bad code -- https://master.php.net/note/delete/100137/bad+code
Del: spam -- https://master.php.net/note/delete/100137/spam
Del: non-english -- https://master.php.net/note/delete/100137/non-english
Del: in docs -- https://master.php.net/note/delete/100137/in+docs
Del: other reasons-- https://master.php.net/note/delete/100137
Reject -- https://master.php.net/note/reject/100137
Search -- https://master.php.net/manage/user-notes.php