Skip to content
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

Use Symfony Stopwatch for timing and memory. #681

Merged
merged 1 commit into from
May 17, 2018
Merged

Conversation

jwage
Copy link
Member

@jwage jwage commented May 16, 2018

Q A
Type feature
BC Break no
Fixed issues #647

Summary

Use the Symfony stopwatch for timing and memory monitoring.

screen shot 2018-05-16 at 5 51 18 pm

@jwage jwage force-pushed the use-symfony-stopwatch branch from 128532b to 0707597 Compare May 16, 2018 22:50
@jwage jwage requested review from Majkl578 and lcobucci May 16, 2018 22:53
@jwage jwage self-assigned this May 16, 2018
@jwage jwage added this to the 2.0 milestone May 16, 2018
@jwage jwage force-pushed the use-symfony-stopwatch branch from 0707597 to fbdd06d Compare May 17, 2018 17:16
@jwage jwage merged commit a86f9ec into master May 17, 2018
@jwage jwage deleted the use-symfony-stopwatch branch May 17, 2018 17:21
{
public function start(string $section) : StopwatchEvent
{
$stopwatch = new SymfonyStopwatch(true);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why creating a new SymfonyStopwatch each time ?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@stof This may have been a misunderstanding on my part of how Stopwatch behaves. Looking at the code now I see that I can have one instance of it. I will make a PR to change it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants