search

jinzhaoyu / speedtracer

Automatically exported from code.google.com/p/speedtracer
0 stars 0 forks source link

Incorrect request timing #42

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
Speed Tracer reports that Chrome is sending out multiple requests (10+) at the 
same time.  Looking at the packets with Wireshark, Chrome is never sending out 
more than 6 concurrent requests.

Even looking at Speed Tracer (see attached screenshot), it is clear that the 
first six responses come back nearly in unison.  The network graph makes it 
seem as though Chrome sent the other requests at the same time and that the 
application cannot handle those additional demands.

What steps will reproduce the problem?
1. Access a web page with CSS and JS in the <head> and 10+ images in the 
<body>.  I was running against a node.js application on port 3000.
2. Look in the Network tab of Speed Tracer (see attached).

Based on what Wireshark is saying, I expect that the first 6 images will be 
requested and responded to *before* a single request for one of the next images 
is made.

Speed Tracer: 0.23

Chrome: 14.0.814.0 dev

Original issue reported on code.google.com by chris....@gmail.com on 17 Jul 2011 at 3:01

Attachments:

GoogleCodeExporter commented 9 years ago 
I am looking at the events coming off the timeline api without processing them 
in Speed Tracer. I see the first six requests start, and the remaining start 
very soon after but before the first six finish loading. Speedtracer shows this 
behavior. I am not sure what you are seeing with Wireshark, but if there is an 
issue it is not with Speed Tracer's interpretation of the data coming in from 
the timeline api.

Original comment by sarahgsm...@google.com on 4 Aug 2011 at 1:48

GoogleCodeExporter commented 9 years ago

Original comment by sarahgsm...@google.com on 4 Aug 2011 at 1:48