Update chrome with new version ( i.e 62) same API content downloading is taking more time than regular. 

- In my Case it almost took 1.26 MS.  

Apols actual time is 1.26 Sec* 

I compared timings in Chrome Developer tools and Fiddler for same API calls. 
and found some differences for Chrome browser. 

Please find attached screenshots for Developer tools and Fiddler timings.
Note: I observed that Overall time in fiddler is showing as downloading in Developer tools 

Deleted: Chrome 10736 API Call timing.PNG 13.1 KB

	Chrome 10736 API Call timing.PNG 13.1 KB View Download

Deleted: Chrome 10736 Fiddler API Call timing.PNG 30.4 KB

	Chrome 10736 Fiddler API Call timing.PNG 30.4 KB View Download

We're also seeing this problem, some additional details:

Example request description:

* Request is JSONP made via script tag insertion in a singly nested same-domain iframe. Request is over http2, no caching.
* Response is small, 350-800 bytes gzipped. Expected Content Download time is < 1ms based on other browsers / previous chrome.
* At the time of the request, there is no contention on the http2 session, this is the first and only request in flight.
* This is also affecting many other requests on live sites, not just our example.

What we've found:

* I have verified via both Chrome's net-internals and wireshark that the content is arriving as expected, within 1ms of first byte. Since the content is small it tends to be sent as 1 packet for the headers and 1-2 for the body arriving very close in time to each other. Even though the network data indicates a complete response received in ~1ms from first byte, we routinely see ~1s Content Download time.
* It does not appear to be just a dev tools UI/data problem, the execution of the response is delayed.
* Does not appear to happen unless dev tools is open, our production timing metrics show no significant change in the timing of this request between C61 and C62.
* Appears to have started with chrome 62, does not happen in 61, seems to still be present in 63-dev
* Disabling http2 via `--disable-http2` flag results in expected timing.

Mostly anecdotal, but after going through many examples: Requests with small response bodies made over http2 seem to have the longest Content Download time. It does also affect requests made over http2 for responses with slightly larger response bodies (~2-3KB), but in most cases I'm seeing Content Download times of 150-300ms there. However, that is still much longer than the actual arrival time of the data.

We are seeing same issue. Ocassionaly chrome takes 3 secs in 'content download'. checking real content download times with wireshark, shows that all tcp packets arrived after 500ms. content size is 5KB of gzipped json data.