问题描述
我们正在向我们服务器上托管的第三方系统发送HTTP WCF请求，并且在发送请求和获取响应之间经历了很长的延迟。第三方声称他们在几秒钟内完成了他们的工作但是在小提琴手中我可以看到 ServerBeginResponse 和 GotResponseHeaders之间存在显着差距。
We are sending a HTTP WCF request to a 3rd party system hosted on our servers and were experiencing a significant delay between sending the request and getting the response. The 3rd party are claiming that they complete their work in a few seconds but in fiddler I can see a significant gap between the ServerBeginResponse and the GotResponseHeaders.
现在我不确定是什么可以解释这种延迟？有人可以解释Fiddler中的 ServerBeginResponse 和 GotResponseHeaders 计时器究竟是什么意思？
Now I'm not sure what could account for this delay? Could someone explain what the ServerBeginResponseand the GotResponseHeaders timers in Fiddler actually mean?
推荐答案
计时器的含义与他们说的完全相同 - 当Fiddler完成向服务器发送HTTP请求时，设置 ServerGotRequest 计时器。当Fiddler从服务器读取完整的响应头集时，会设置 GotResponseHeaders 计时器。
The timers mean pretty much exactly what they say-- The ServerGotRequest timer is set when Fiddler is done transmitting the HTTP request to the server. The GotResponseHeaders timer is set when Fiddler has read the complete set of response headers from the server.
在屏幕截图中， ServerBeginResponse （在返回服务器响应的第一个字节时设置）与之间存在巨大延迟> GotResponseHeaders ，这表明服务器花了大量时间完成HTTP响应标头的返回。
In your screenshot, there's a huge delay between ServerBeginResponse (which is set when the first byte of the server's response is returned) and GotResponseHeaders which suggests that the server spent a significant amount of time in completing the return of the HTTP response headers.
如果您发送给我（通过帮助>发送反馈）这个流量的SAZ捕获，我可以仔细看看它。
If you send me (via Help > Send Feedback) a SAZ capture of this traffic, I can take a closer look at it.
这篇关于了解提琴手统计数据的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！