TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

Switching Apache from Prefork to Worker MPM in RHEL / CentOS 5.x / Fedora 13

3 点作者 jqueryin将近 15 年前

2 条评论

chuhnk将近 15 年前
Prefork requires a process per request whereas Worker only requires a thread per request. So say you've got 20 processes in prefork taking 100mb each. You can server 20 concurrent requests and its using 2gb of memory. Where as with worker mpm there will be say 4 processes each with 20-30 threads. Thats going to be 400mb and an ability to serve 80-120 requests concurrently.<p>If you do go the worker route, my advice is to use mod_fastcgi rather than mod_fcgid for performance and stability reasons. Also look around for the patch which fixes the timeout errors that sporadically occur.<p>Worker MPM is definitely the way to go when running apache, something that is overlooked because not many people are aware of it or how to configure it. Beyond that there is also event mpm which was experimental but is now stable I believe.
Scott_MacGregor将近 15 年前
We looked at worker but decided that for us, prefork met our needs better. Nice article though, good job, I enjoyed reading it.