First of all, let me say that Speedtracer has become my new best friend! As a
web applications developer facing performance issues, this is absolutely
everything I need and a bunch of stuff I didn't even know I could get, all
packaged into one! I am like a kid at Christmas with a new toy. Anyway, thanks
for your hard work on this. Keep up the great work. I personally thank you for
making my job a whole lot easier.
Potential Features:
1. Allow horizontal scrolling in the Main Graph (at top) and details timeline
(below) so that you don't have to re-size the Overview Graph to move down the
timeline. It would keep the same timeline window (End Slider-Start
Slider=Selected Timeline "Window"), but just move the window down the overview
graph as you scroll horizontally. So, say you have a 2 second window selected
from @100ms to @2100ms. If you scroll to the right, it would move that same 2
second window down the timeline (e.g. @200ms-@2200ms, @300ms-@2300ms, etc.).
Saves time constantly re-sizing just to see the next events.
2. There are no Y-axis labels on the Main and Overview Graph (timeline)
windows. So, things like network connections don't tell you how many network
connections were open at a particular point in the timeline. Either providing
Y-axis labels or hover text that tells you the number of connections where your
mouse currently is, would be nice.
3. I'm not entirely sure if this is accurate, but it seems like when
transitioning from page to page, the previous page continues recording, even
though the events should now be applying to the next page. If I'm mistaken,
please just ignore this one.
4. Ensure that timeline (Network Resource Details request & response) bars are
able to be seen entirely. The long ones go off the right-side of the page and
because you can't scroll horizontally in the details area, you can't visualize
the request and response times). This happens even with the overview graph
showing the entire capture.
5. Provide totals in the details section regarding total time, total bytes
transferred, etc. When filtering have these totals only represent what's
showing. So, if I want to see a total of how many bytes all scripts are, I
filter on scripts and look at the total. If I want to see a total of how much
time it took all rendering to occur, I filter by rendering and look at the
total time. The benefit is that I want to know what percentages of TOTAL time,
bytes, etc. things are taking. How much time is it taking overall for
rendering, for javascript parsing, etc.
Just some ideas. Again, please ignore me if these already exist and I'm just
not understanding. I'm a new user to this. Keep up the great work!
Thanks,
Nathon Dalton
Original issue reported on code.google.com by nadal...@gmail.com on 26 Jul 2012 at 6:37
Original issue reported on code.google.com by
nadal...@gmail.comon 26 Jul 2012 at 6:37