多应用+插件架构,代码干净,二开方便,首家独创一键云编译技术,文档视频完善,免费商用码云13.8K 广告
# Apache MPM beos | [说明](#calibre_link-11) | This Multi-Processing Module is optimized for BeOS. | | --- | --- | | [状态](#calibre_link-12) | MPM | | [模块名](#calibre_link-13) | mpm_beos_module | | [源文件](#calibre_link-14) | beos.c | ### 概述 This Multi-Processing Module (MPM) is the default for BeOS. It uses a single control process which creates threads to handle requests. ## MaxRequestsPerThread 指令 | [说明](#calibre_link-18) | Limit on the number of requests that an individual thread will handle during its life | | --- | --- | | [语法](#calibre_link-19) | `MaxRequestsPerThread number` | | [默认值](#calibre_link-24) | `MaxRequestsPerThread 0` | | [作用域](#calibre_link-20) | server config | | [状态](#calibre_link-21) | MPM | | [模块](#calibre_link-22) | beos | `MaxRequestsPerThread` directive sets the limit on the number of requests that an individual server thread will handle. After `MaxRequestsPerThread` requests, the thread will die. If `MaxRequestsPerThread` is `0`, then the thread will never expire. Setting `MaxRequestsPerThread` to a non-zero limit has two beneficial effects: * it limits the amount of memory that a thread can consume by (accidental) memory leakage; * by giving threads a finite lifetime, it helps reduce the number of threads when the server load reduces. ### 注意: For `KeepAlive` requests, only the first request is counted towards this limit. In effect, it changes the behavior to limit the number of _connections_ per thread.