Can anyone tell me, where to find the xdebug profiler output? In xdebug.ini, profiler is permanently

UU07J5ZGC

Can anyone tell me, where to find the xdebug profiler output? In xdebug.ini, profiler is permanently activated (to eliminate issues with remote enabling) and the output path ist specified:

zend_extension=xdebug.so
xdebug.profiler_enable=1
xdebug.trace_enable_trigger=1
xdebug.profiler_enable_trigger=1
xdebug.remote_autostart=1
xdebug.remote_enable=1
xdebug.remote_host=${SPRYKER_XDEBUG_HOST_IP}
xdebug.remote_port=9000
xdebug.profiler_output_dir=/tmp/xdebug/profiler
xdebug.trace_output_dir=/tmp/xdebug/trace
# This is needed to prevent max recursion exception when Twig templates are very complicated
xdebug.max_nesting_level=1000

I'm using Docker environment. The containers are started with -x, but in CLI container, /tmp directory stays empty. Any ideas?

Ievgen Varava

are you sure that profiler is active? it would significantly slow down the system

Ievgen Varava

it definitely should use provided output dir

sprymiker

Just an idea:
Try to set xdebug.profiler_enable_trigger=0
To be sure it is always activated by xdebug.profiler_enable=1

Ievgen Varava

In order to prevent the profiler to generate profile files for each request, you need to set *xdebug.profiler_enable* to 0 so this should not prevent profiling of each request

Ievgen Varava

I would rather pay attention to https://xdebug.org/docs/all_settings#profiler_output_dir

Ievgen Varava

maybe directory does not exist and user have no rights to create it

UU07J5ZGC

Thanks for your ideas. Just to be sure, I've set the xdebug.*_enable_trigger settings to 0:

UU07J5ZGC

But I can still see no profiler output in /tmp/ inside the CLI container. I also can't see any real performance impact when browsing through ZED 🤔 (but phpinfo states the profiler to be enabled)

sprymiker

Just to clarify…

If you run docker/sdk cli -x it is only means that console commands run there are profiled.

If you need to profile Zed Backoffic -
docker/sdk run -x
And then look into

docker exec -it spryker_zed_eu_1 bash

(container name can vary depends on deploy yml)

sprymiker

But I would suggest Blackfire instead. You can find unfinished PR at https://github.com/spryker/docker-sdk/pull/87

sprymiker

https://github.com/spryker/docker-php/pull/13 is also related

UU07J5ZGC

I'm starting my containers with docker/sdk up -x. The CLI container is only used for checking the output dir (which stays empty after browsing ZED). Even if I connect to the zed container directly, /tmp/ stays empty

sprymiker

No sense to run cli to check output dir, as /tmp folder is not shared between containers.

sprymiker

What if if you run console command in cli -x ? Still empty?

U01DHAW94DQ

I've solved a similar problem, by mkdir -p /tmp/xdebug/profiler && chmod a+w /tmp/xdebug/profiler

sprymiker

It seems we need to initialize it in Dockerfile. Thanks for the catch.