Hi!
On Sun, 27 Feb 2011, oren[@]triond.com wrote:
> I would like to be able to trigger profiling on certain system events,
> such as process characteristics (CPU or mem usage), script runtime
> (above X seconds) etc.
>
> As I understand now, the only way to trigger profiling is either for
> all scripts, or through a cookie.
>
> I believe that triggering profiling on such events will make profiling
> much more focused. Right now if I want to catch a use case that
> happens 1 percent of the time, but generates 20 percent of the load, I
> have no way of pin-pointing it.
As you might have understood because of the late reply; I am rather
busy. Could you do me a favour and file this as a feature request at
http://bugs.xdebug.org ? I don't know how easy this would be though, as
currently profiling has to start from the beginning of the script. What
most likely will need to happen is that profiling is still done for
every script, but all the runs that do not match the criteria are
removed.
cheers,
Derick
-- Like Xdebug? Consider a donation: http://xdebug.org/donate.php Xdebug | http://xdebug.org | xdebug-general@lists.xdebug.org twitter: @derickr and @xdebugReceived on Mon Mar 14 2011 - 06:48:52 GMT
This archive was generated by hypermail 2.2.0 : Mon Jun 25 2018 - 06:00:04 BST