What are the Slack Archives?
Itβs a history of our time together in the Slack Community! Thereβs a ton of knowledge in here, so feel free to search through the archives for a possible answer to your question.
Because this space is not active, you wonβt be able to create a new post or comment here. If you have a question or want to start a discussion about something, head over to our categories and pick one to post in! You can always refer back to a post from Slack Archives if needed; just copy the link to use it as a reference..
Can anyone tell me, where to find the xdebug profiler output? In xdebug.ini, profiler is permanently
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?
Comments
-
are you sure that profiler is active? it would significantly slow down the system
0 -
it definitely should use provided output dir
0 -
Just an idea:
Try to set xdebug.profiler_enable_trigger=0
To be sure it is always activated by xdebug.profiler_enable=10 -
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 request0 -
I would rather pay attention to https://xdebug.org/docs/all_settings#profiler_output_dir
0 -
maybe directory does not exist and user have no rights to create it
0 -
Thanks for your ideas. Just to be sure, I've set the
xdebug.*_enable_trigger
settings to 0:0 -
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)
0 -
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 intodocker exec -it spryker_zed_eu_1 bash
(container name can vary depends on deploy yml)
0 -
But I would suggest Blackfire instead. You can find unfinished PR at https://github.com/spryker/docker-sdk/pull/87
0 -
https://github.com/spryker/docker-php/pull/13 is also related
0 -
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
0 -
No sense to run cli to check output dir, as /tmp folder is not shared between containers.
0 -
What if if you run console command in
cli -x
? Still empty?0 -
I've solved a similar problem, by
mkdir -p /tmp/xdebug/profiler && chmod a+w /tmp/xdebug/profiler
0 -
It seems we need to initialize it in Dockerfile. Thanks for the catch.
0
Categories
- All Categories
- 42 Getting Started & Guidelines
- 7 Getting Started in the Community
- 8 Additional Resources
- 7 Community Ideas and Feedback
- 76 Spryker News
- 929 Developer Corner
- 787 Spryker Development
- 89 Spryker Dev Environment
- 362 Spryker Releases
- 3 Oryx frontend framework
- 35 Propel ORM
- 68 Community Projects
- 3 Community Ideation Board
- 30 Hackathon
- 3 PHP Bridge
- 6 Gacela Project
- 26 Job Opportunities
- 3.2K π Slack Archives
- 116 Academy
- 5 Business Users
- 370 Docker
- 551 Slack General
- 2K Help
- 75 Knowledge Sharing
- 6 Random Stuff
- 4 Code Testing
- 32 Product & Business Questions
- 70 Spryker Safari Questions
- 50 Random