Firebase跟踪显示错误的中值时间延迟? [英] Firebase trace showing wrong median time latency?

问题描述

我正在我的应用程序中添加Firebase性能跟踪，下面的图像是最后一个24 Hrs

I am adding Firebase performance trace in my app and below image is data for last 24 Hrs

您可以看到Median是647ms，其中95%时间延迟是14.81s，而对于5%，时间延迟是460ms.

As you can see the Median is 647ms, where as 95% time latency is 14.81s and for 5% it is 460ms.

中位数如何为647ms，应该接近14秒?我在这里想念什么吗?

How can the median be 647ms, it should be near around 14 sec? Am I missing something here?

编辑-

在下面的图像数据是最后一个7 days

In below image data is for last 7 days

正如您在上一个24 Hrs中看到的那样，我有95th个百分位数是14.81s的数据，但是在最近7天的图表中如何没有提到14 secs跟踪?所有迹线都在5.95s下?

As you can see in last 24 Hrs I had data where 95th percentile was 14.81s, but how can in last 7 days graph there is no mention of the 14 secs trace? all traces are below 5.95s?

分布图像中的等待时间也在460 ms到2.94s之间，但是由于第一个图像中的第95个百分位数是14.81s，而在第二个图像中它是5.95s，但是分布仅显示了460ms-2.94s之间的数据?那么，该分布数据显示什么?他们不应该在这里显示最近7天所有请求的时间延迟吗?

Also in the distribution image latency is between 460 ms to 2.94s but as 95th percentile in first image is 14.81s and in second image it is 5.95s but distribution is only showing data between 460ms-2.94s? Then what is this distribution data showing? Shouldn't they show here all requests time delay in the last 7 days?

当我检查设备样本时

所有情况下的最大时延最大值是5.60s而不是14.81s?

the time delay maximum in all cases is 5.60s not 14.81s?

推荐答案

95％并不意味着95％的时间，它是值范围内的第95个百分位数，不要与频率混淆.

95% does not mean 95% of the time, it is the 95th percentile in the value range, not to be confused with frequency.

您的大多数执行"(90％)将在5-95％之间，因此中位数为647毫秒是合理的.

Most (90%) of your "executions" will be between 5-95% so it makes sense that the median is 647 ms.

我不知道95％的值到底是什么，它可能是前5％执行时间的平均值，也可能是该范围内的第一个值.

I don't know exactly what the 95% value represents, it could be an average of the top 5% execution times or it could be the first value in the range.

这篇关于Firebase跟踪显示错误的中值时间延迟?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！