Skip to content

Profiler: Profiles cleanup as of 6.3 #17631

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Dec 30, 2022
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion console/calling_commands.rst
Original file line number Diff line number Diff line change
Expand Up @@ -58,6 +58,6 @@ method)::

.. note::

Most of the times, calling a command from code that is not executed on the
Most of the time, calling a command from code that is not executed on the
command line is not a good idea. The main reason is that the command's
output is optimized for the console and not to be passed to other commands.
11 changes: 10 additions & 1 deletion profiler.rst
Original file line number Diff line number Diff line change
Expand Up @@ -35,10 +35,19 @@ Symfony Profiler, which will look like this:
in the ``X-Debug-Token-Link`` HTTP response header. Browse the ``/_profiler``
URL to see all profiles.

.. versionadded:: 6.3

Profile garbage collection was introduced in Symfony 6.3.

.. note::

To limit the storage used by profiles on disk, they are probabilistically
removed after 2 days.

Accessing Profiling Data Programmatically
-----------------------------------------

Most of the times, the profiler information is accessed and analyzed using its
Most of the time, the profiler information is accessed and analyzed using its
web-based interface. However, you can also retrieve profiling information
programmatically thanks to the methods provided by the ``profiler`` service.

Expand Down