Add tooling for enabling/disabling xdebug profiler #105
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
tormi
requested changes
Mar 5, 2020
|
There's also issue at official Lando lando/lando#1954 (for Apache) Maybe something to borrow |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Feature
This adds a tooling which allows developers to easily enable and disable the xdebug profiler when needed.
The profiler generates
cachegrind.out.files in the /app directory which could be loaded to KCacheGrind (and similar) application for further analysis.Note that this requires a working xdebug setup and assumes that xdebug is enabled (see
lando xdebug-on)Usage:
lando xdebug-profiler-onlando xdebug-profiler-off