Request time is wrong

[AykutCevik]

The request time (in ms) is not the actual time of the request, but the sum of the whole procedure of the POSTMan request itself.

So the value itself is not accurate and can not be used for any benchmarking purposes - thus it's unnecessary.

What I need is just the time of the request itself like it is shown in the Google Chrome developer tool network overview.

To reconstruate this:
If I'm in my "collection view", the request time is shown far less than that in the "history view" for the same request. The reason for this is, that my history itself is really huge. So at every request, the history refreshes and the CPU time for this operation is also added to the request time.

[AykutCevik]

Should mention, that I'm not using the packaged app.

[abhijitkane]

AFAIK, There's no way to get the actual response time that's shown in the dev tools. Any items in the event loop that have to occur after the request is sent, but before the response is processed will add to the time that's shown in the Postman app.

I saw a difference of 5-8ms between the two values, not the difference you saw, but there may have been a delay in processing the response in your app. Are you consistently seeing such huge differences in the two shown times?

[AykutCevik]

Yes, I'm consistently seeing such huge differences in the two shown times. As I mentioned, the larger the history, the higher the response time.

I think, that POSTman does a lot of post-request actions, but the time is calculated at the end of all the actions. I would move the time calculation directly in the "done"-event of each request.

[abhijitkane]

That fix has already been made, and we'll push it in the next release.

[AykutCevik]

Nice, thanks!

[abhijitkane]

Fixed in 1.0.4

[GF-Huang]

Incorrect again.

---

---

---

[saswatds]

Hi @greatfirewall, The Chome browser is able to achieve much lower time due to internal caching.
As of App version v7.1.1, if you hover over the time display you will be able to see with much granularity what aspect of the request is taking so much time.

As an example, for the very first request here the time taken is much longer due to DNS lookup and TCP and SSL Handshake.

Sending the same request again results in a much lesser time

If you are still finding the time taken by postman is much longer then feel free to get back to us.

Thanks