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

Improve Profiler Layout #74

Closed
florianpreusner opened this issue Nov 2, 2016 · 12 comments
Closed

Improve Profiler Layout #74

florianpreusner opened this issue Nov 2, 2016 · 12 comments

Comments

@florianpreusner
Copy link
Member

Some textareas are pretty small by default. This should be improved. Also some new screenshots should be created and inserted into README.md.

@florianpreusner florianpreusner added this to the v6.0 milestone Dec 12, 2016
@florianpreusner florianpreusner removed this from the v6.0 milestone Sep 29, 2017
@Neirda24
Copy link
Contributor

Also it would be nice to have some time results in the profiler. Maybe using http://guzzle.readthedocs.io/en/latest/request-options.html#on-stats ?

@gregurco
Copy link
Member

@Neirda24 yep, it's really good idea. But I'm not sure if we can use this option. This option is allowed only for requests, not for clients and probably we need to collect execution time in another way. I'm trying to find the solution 🙂

@Neirda24
Copy link
Contributor

@gregurco : agreed. Another way would be to add a middleware at the beginning and another at the end. each of the same instance recording the start time and the end time per requests.

@gregurco
Copy link
Member

@Neirda24 in this case you will not know the exact time. It will be very approximate. Here you can see how guzzle calculates time for on_stats callback:

For different handlers there are different methods. Yep, probably it should be middleware, but somehow in another way.

@Neirda24
Copy link
Contributor

@gregurco : I see... Why can't we use the on_stats method ? We can add it as default option on the client. (I didn't made any research on this subject as of now...)

@gregurco
Copy link
Member

@Neirda24 the main problem is that default client option can be easy rewritten by request option and you will not be able to calculate time correctly 🙁

@Neirda24
Copy link
Contributor

@gregurco : Fair enough. keep me posted if you have any ideas. I'll be glad to help.

@andheiberg
Copy link

@Neirda24 the main problem is that default client option can be easy rewritten by request option and you will not be able to calculate time correctly 🙁

Could you elaborate on this?

I'm not sure I understand why this wouldn't be trivial to implement?

@gregurco
Copy link
Member

gregurco commented Jan 19, 2018

@andheiberg calculation of all requests time was done in PR #156 and released in v7.3.0

@andheiberg
Copy link

andheiberg commented Jan 29, 2018

@gregurco thanks for your response.

See https://github.com/ludofleury/GuzzleBundle for the split between connection and response timing.

See https://github.com/e-moe/guzzle6-bundle specifically for how they have accurate time lines in the symfony profiler.

I don't believe either is currently functional in this package.

@gregurco
Copy link
Member

@andheiberg no, for now we just calculate total time for each request and time for all requests. In future releases probably we will add more information related to request time.

@florianpreusner
Copy link
Member Author

Some improvements are already implemented. Visualization of timings of each request were implemented in #208 👏

To keep this topic (improvements for profiler) a little bit cleaner we created a new issue (#210) and will close this one.

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

No branches or pull requests

4 participants