View previous topic :: View next topic |
Author |
Message |
cjubon Guru


Joined: 03 Jul 2007 Posts: 450 Location: Vienna/Europe
|
Posted: Fri Aug 15, 2008 10:27 am Post subject: resources needed by different apache2_mpms |
|
|
On my desktop machine, I've installed apache. I'm not interested in performance, since it's a testing server for web-development and doesn't connect to outside my LAN (hopefully ).
I have two install options: - APACHE2_MPMS="prefork" and USE="-threads" (which needs an extra entry in /etc/portage/package.use because threads is enabled globylly in /etc/make.conf), or
- APACHE2_MPMS="worker" USE="threads" where using threads would be my default configuration.
Now I just wondered which setup uses less resources (I mean CPU and RAM). It's not that important, but it would be interesting.
Thanks for your answers. _________________ Mandrake Dec 2001 · Debian "Woody" Aug 2002 · Gentoo Jan 2004 · Funtoo Oct 2009 |
|
Back to top |
|
 |
manaka Apprentice


Joined: 23 Jul 2007 Posts: 178 Location: Spain
|
Posted: Fri Aug 15, 2008 4:21 pm Post subject: |
|
|
Prefork mpm uses one process for every request. It's the most tested and stable mpm. But it's memory hungry.
Worker mpm aims at reducing memory usage. It uses a mixed process/thread architecture. As a drawback, requests are not isolated anymore. If one process dies, all its threads die, affecting many requests.
As for the CPU usage, I would bet it's similar. _________________ Javier Miqueleiz
"Listen to your heart. It knows all things, because it came from the Soul of the World, and it will one day return there." |
|
Back to top |
|
 |
cjubon Guru


Joined: 03 Jul 2007 Posts: 450 Location: Vienna/Europe
|
Posted: Sat Aug 16, 2008 11:55 am Post subject: |
|
|
Thanks for the answer, manaka. I seems I'll stick with prefork. _________________ Mandrake Dec 2001 · Debian "Woody" Aug 2002 · Gentoo Jan 2004 · Funtoo Oct 2009 |
|
Back to top |
|
 |
|