有人可以解释这些apache替补结果,有什么突出的东西吗? [英] Can someone interpret these apache bench results, is there something that stands out?

查看:142
本文介绍了有人可以解释这些apache替补结果,有什么突出的东西吗?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

以下是一个apache工作台运行10个请求,有50个并发线程。

Below is a apache bench run for 10K requests with 50 concurrent threads.

我需要帮助理解结果,结果中有什么突出的东西可能指向阻塞和限制的东西每秒更多的请求?

I need help understanding the results, does anything stand out in the results that might be pointing to something blocking and restricting more requests per second?

我正在查看连接时间部分,并看到'等待'和'处理'。它显示等待的平均时间是208,连接的平均时间是0,处理是208 ..但是总数是208.有人可以解释这个,因为它对我没有多大意义。

I'm looking at the connection time section, and see 'waiting' and 'processing'. It shows the mean time for waiting is 208, and the mean time to connect is 0 and processing is 208..yet the total is 208. Can someone explain this to me as it doesn't make much sense to me.

推荐答案

连接时间是与服务器建立连接所花费的时间。您可能在同一服务器或局域网内运行它,因此您的连接时间为0.
处理时间是服务器处理和发送完整响应所花费的总时间。
等待时间是发送请求和接收第一个响应字节之间的时间。

Connect time is time it took ab to establish connection with your server. you are probably running it on same server or within LAN, so your connect time is 0. Processing time is total time server took to process and send complete response. Wait time is time between sending request and receiving 1st byte of response.

同样,由于您在同一台服务器上运行,和文件的小尺寸,你的处理时间==等待时间。

Again, since you are running on same server, and small size of file, your processing time == wait time.

对于真正的基准测试,请尝试从目标市场附近的多个点开始,以了解延迟。现在你所拥有的所有信息都是等待时间。

For real benchmark, try ab from multiple points near your target market to get real idea of latency. Right now all the info you have is the wait time.

这篇关于有人可以解释这些apache替补结果,有什么突出的东西吗?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆