If I wanted to to monitor response time of my requests should I use Apache's mod_status or should I use Passenger's passenger-status monitoring tools?
如果我想监视请求的响应时间，我应该使用Apache的mod_status，还是应该使用乘客的乘客状态监控工具?
My concern is that enabling mod_status will slow my apps down, but I don't have anyway to compare since I need to run mod_status to benchmark the performance.
我担心的是，启用mod_status会降低我的应用程序的速度，但是我没有必要进行比较，因为我需要运行mod_status来测试性能。
By the way Passenger's passenger-status only gives me some trivial info like so:
顺便说一下，乘客的乘客身份只给了我一些简单的信息:
----------- General information -----------
max = 6
count = 0
active = 0
inactive = 0
Waiting on global queue: 0
----------- Domains -----------
...
2 个解决方案
#1
3
I don't believe this should have any impact on Apache's performance.
我不认为这会对Apache的性能产生任何影响。
Pretty much all the module is doing is taking internal state that the server already has — i.e. it knows how many workers it has spawned, what they're doing and so on — and rendering it to HTML.
几乎所有模块所做的就是获取服务器已经拥有的内部状态——例如，它知道它已经生成了多少worker，它们正在做什么等等——并将其呈现给HTML。
#2
1
Just for your information: I have a apache version 2.2.16 running receiving live traffic (so not a benchmark). No ruby or passenger, but with mod_fastcgi.
仅供参考:我有一个正在运行的apache 2.2.16版本，正在接收实时流量(所以不是基准)。不是ruby或passenger，而是mod_fastcgi。
At 175req/s the server kept up, at 370 it was running at a load of 8-10.
在175req/s服务器继续运行，在370的时候它的负载是8-10。
After disabling the Extended status (but keeping mod_status enabled), the load dropped below 2.
在禁用扩展状态(但保持mod_status为启用状态)之后，负载降低到2以下。
Disabling mod_status completely did not make any difference over disabling Extended (load may already be too low to see a difference now).
禁用mod_status完全没有对禁用扩展造成任何影响(现在负载可能已经太低，无法看到差异)。
#1
3
I don't believe this should have any impact on Apache's performance.
我不认为这会对Apache的性能产生任何影响。
Pretty much all the module is doing is taking internal state that the server already has — i.e. it knows how many workers it has spawned, what they're doing and so on — and rendering it to HTML.
几乎所有模块所做的就是获取服务器已经拥有的内部状态——例如，它知道它已经生成了多少worker，它们正在做什么等等——并将其呈现给HTML。
#2
1
Just for your information: I have a apache version 2.2.16 running receiving live traffic (so not a benchmark). No ruby or passenger, but with mod_fastcgi.
仅供参考:我有一个正在运行的apache 2.2.16版本，正在接收实时流量(所以不是基准)。不是ruby或passenger，而是mod_fastcgi。
At 175req/s the server kept up, at 370 it was running at a load of 8-10.
在175req/s服务器继续运行，在370的时候它的负载是8-10。
After disabling the Extended status (but keeping mod_status enabled), the load dropped below 2.
在禁用扩展状态(但保持mod_status为启用状态)之后，负载降低到2以下。
Disabling mod_status completely did not make any difference over disabling Extended (load may already be too low to see a difference now).
禁用mod_status完全没有对禁用扩展造成任何影响(现在负载可能已经太低，无法看到差异)。