Warning: You are browsing the documentation for Symfony 2.4, which is no longer maintained.
Read the updated version of this page for Symfony 6.0 (the current stable version).
Table of Contents
The Stopwatch component provides a way to profile code.
New in version 2.2
The Stopwatch component was introduced in Symfony 2.2. Previously, the
Stopwatch class was located in the HttpKernel component.
You can install the component in two different ways:
The Stopwatch component provides an easy and consistent way to measure execution time of certain parts of code so that you don't constantly have to parse microtime by yourself. Instead, use the simple Stopwatch class:
1 2 3 4 5 6 7
use Symfony\Component\Stopwatch\Stopwatch; $stopwatch = new Stopwatch(); // Start event named 'eventName' $stopwatch->start('eventName'); // ... some code goes here $event = $stopwatch->stop('eventName');
You can also provide a category name to an event:
You can consider categories as a way of tagging events. For example, the Symfony Profiler tool uses categories to nicely color-code different events.
As you know from the real world, all stopwatches come with two buttons: one to start and stop the stopwatch, and another to measure the lap time. This is exactly what the lap() method does:
1 2 3 4 5 6 7 8 9
$stopwatch = new Stopwatch(); // Start event named 'foo' $stopwatch->start('foo'); // ... some code goes here $stopwatch->lap('foo'); // ... some code goes here $stopwatch->lap('foo'); // ... some other code goes here $event = $stopwatch->stop('foo');
Lap information is stored as "periods" within the event. To get lap information call:
In addition to periods, you can get other useful information from the event object. For example:
1 2 3 4 5 6 7
$event->getCategory(); // Returns the category the event was started in $event->getOrigin(); // Returns the event start time in milliseconds $event->ensureStopped(); // Stops all periods not already stopped $event->getStartTime(); // Returns the start time of the very first period $event->getEndTime(); // Returns the end time of the very last period $event->getDuration(); // Returns the event duration, including all periods $event->getMemory(); // Returns the max memory usage of all periods
Sections are a way to logically split the timeline into groups. You can see how Symfony uses sections to nicely visualize the framework lifecycle in the Symfony Profiler tool. Here is a basic usage example using sections:
1 2 3 4 5 6 7
$stopwatch = new Stopwatch(); $stopwatch->openSection(); $stopwatch->start('parsing_config_file', 'filesystem_operations'); $stopwatch->stopSection('routing'); $events = $stopwatch->getSectionEvents('routing');
You can reopen a closed section by calling the openSection() method and specifying the id of the section to be reopened:
1 2 3
$stopwatch->openSection('routing'); $stopwatch->start('building_config_tree'); $stopwatch->stopSection('routing');