[英]Will enabling `mod_status` in apache slow my app down?
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
还是应该使用Passenger的passenger-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 -----------
...
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 — ie it knows how many workers it has spawned, what they're doing and so on — and rendering it to HTML. 几乎所有模块正在做的是采取服务器已经拥有的内部状态 - 即它知道它产生了多少工人,他们正在做什么等等 - 并将其呈现为HTML。
Just for your information: I have a apache version 2.2.16 running receiving live traffic (so not a benchmark). 仅供参考:我有一个运行接收实时流量的apache版本2.2.16(因此不是基准测试)。 No ruby or passenger, but with mod_fastcgi. 没有红宝石或乘客,但有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. 禁用Extended
状态(但保持启用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与禁用Extended没有任何区别(加载可能已经太低而无法立即看到差异)。
声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.