1471170 - Integrated Network And Performance View

Status: RESOLVED INVALID

(DevTools :: Performance Tools (Profiler/Timeline), enhancement, P3)

Description

[Dave Hawkins]

I'd like to be able to see network calls in the peformance waterfall. Currently it's impossible to see the relationship between client processing and network calls. One use case I'm interested in is analysing whether it's possible to concurrently execute page initialisation while fetching remote data and confirming that changes to achieve that are working as expected.

Comment 1

[Julien Wajsberg [:julienw]]

Hey Dave,
thanks for the bug report!

Please note that we don't plan to add new features to the current performance panel, but are very busy creating a new performance tool. 

That performance tool just started adding support for network features, but we definitely plan to be able to see both network and processing on one view.

It's not ready for general consumption yet, especially it gives a lot of useless data for normal web developers, but shall you want to try it, you can access it at http://perf-html.io/.
You can also enable it in Firefox, from the devtools' settings. But I'd advise against this solution for now, so that you can keep using the 2 tools separately for now.


I have a last remark about your comment: be careful as what you test on your own machine is likely not what your users can see. Always take the result of performance tools with a grain of salt :-)

Comment 2

[Dave Hawkins]

Hi Julien,

Does this mean there's no point in logging any further enhancements - I have others to log - or will they be taken into consideration for your new tool?

I realise performance tools are sensitive to the environment, but I'd be a bit worried if there was no correlation between these different environments. However, in any case, I have several development environments that should be set up in a similar manner to our various users.

Comment 3

[Julien Wajsberg [:julienw]]

To be clearer, we're changing the UI but both tools share the same underlying collecting code (or at least part of it).

TBH we're quite in the middle of our path at the moment: the new tool isn't good enough for web developers who aren't our main focus now, but we don't actively work on the old tool (merely fixing bugs) which is good but imperfect.

I think filing bugs for enhancement is always a good thing, this can help driving our future work towards web developers.

Comment 4

[Greg Tatum [:gregtatum]]

Hey Dave,

It sounds like you have lots of great ideas and thoughts on performance DevTools. As Julien mentioned, we're actively working on some new performance tooling, and only fixing regressions on the DevTools panel right now.

We'd love to get your feedback and involvement on our new tooling: https://github.com/devtools-html/perf.html

Eventually we are going to be migrating our changes back to DevTools, but we have been prioritizing features for Gecko engineers to help make Firefox faster.

We have docs on the use of the new tooling here: https://perf-html.io/docs/

We have docs on the development process here: https://github.com/devtools-html/perf.html/tree/master/docs-developer

I'd also encourage you to hit us up on slack, where we talk about the development process on the #perf channel: https://devtools-html-slack.herokuapp.com/

Comment 5

[Jan Honza Odvarko [:Honza] (always need-info? me)]

This report is related to the old DevTools Profiler.
The Performance panel now points to the new Firefox profiler available at profiler.firefox.com
Closing as Invalid bug