Re: [pdt-dev] xDebug profiller

[Michele Locati <michele@xxxxxxxxx>]

Hi David,

1. Yes, I'd prefer a checkbox in "profile" launch instead of adding a new "profile and debug" profile

2. Would that work also when the server is not directly controlled by PDT (like Apache or NGINX)?

3. I'd prefer a profile session for each request: profiling is very helpful to see where a request is taking a lot of time, and mixing requests in the same session would make it harder.

4. What about adding a filter for the Content-Type response header? We could also add a filter for paths (eg "I want to profile the requests that starts with "/path/to/uri/resource/")

5. I don't understand ;)

--

Michele

2018-04-28 19:11 GMT+02:00 Dawid Pakuła <zulus@xxxxxxxxx>:

Hi Team,

I’m playing with xDebug profiler and thinking about possible integration.

Currently I have couple concerns:

1. We need support PROFILE and PROFILE+DEBUG mode. I think debug as optional checkbox in profile launch configuration. What you think?

2. For web launch we need place where to store “xdebug.profiler_output_dir”. For EXE we can easy read (or override) this property before launch. What you think about settings in server configuration + ability to override on web launch level?

3. I’m not sure how to play with multiple request. Auto aggregate or prepare profile session for each request?

4. Despite of aggregation we definetely need way to filter requests. Any idea how to prepare usable UI for that?

5. I’m not sure how efficiently watch SSH dir changes for new profile files. Any ideas?

Besides I want extend “import profile session” wizard to support xdebug cache-grind files (“simple" transform). This I hope will be good start before implement watch deamons.

_______________________________________________
pdt-dev mailing list
pdt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/pdt-dev