Advertisement: Linux VPS for $4/month - based on OpenVZ, credit card accepted, automatic setup.
+ Post New Thread
Results 1 to 2 of 2

Thread: cPanel/WHM: Apache MPM Prefork or Worker? differences

  1. #1
    Fli
    Fli is offline
    Administrator Fli's Avatar
    Join Date
    Mar 2013
    Posts
    2,474

    cPanel/WHM: Apache MPM Prefork or Worker? differences



    On WHM/cPanel server,

    Apache Mod_QoS module requires Apache Worker to be used instead of default Apache Prefork. Apache Prefork MPM (Multi-Processing Module) is set as "recommended" by WHM/cpanel. They say it is because of the stability.

    So is it safe to switch to Worker MPM? What are differences?

    Prefork MPM uses multiple child processes with one thread each and each process handles one connection at a time.

    Worker MPM uses multiple child processes with many threads each. Each thread handles one connection at a time.
    Source: http://codebucket.co.in/apache-prefork-or-worker/

    So prefork is using one process per one connection, Worker is using one process with multiple "threads" to serve more connections per process.

    Worker is said to use less RAM, Prefork to be more "stable" or process "isolated".

    Details on both MPM:
    Prefork: https://httpd.apache.org/docs/2.2/mod/prefork.html
    Worker: https://httpd.apache.org/docs/2.2/mod/worker.html

    More description on MPMs, comparison: http://serverfault.com/a/383634

  2. #2
    Junior Member gexacor's Avatar
    Join Date
    Jul 2016
    Posts
    4


    Is this useful / helpfull? Yes | No
    Quote Originally Posted by admin View Post
    So prefork using one process per one connection, Worker is using one process with multiple "threads" to serve more connections per process.
    Worker is said to use less RAM, Prefork to be more "stable" or process "isolated".
    I'm using prefork on all my servers for a long time and happy with that.
    It's only can be a problem if max processes count not configured properly and you servers have more clients that it can serve.
    That situation should be treated correctly on httpd.conf file, that's not a big deal.

+ Post New Thread

Similar Threads

  1. Replies: 4
    Last Post: 05-22-2018, 01:31 PM
  2. Replies: 1
    Last Post: 05-16-2018, 09:01 AM
  3. Replies: 0
    Last Post: 06-18-2017, 08:45 PM
  4. Replies: 0
    Last Post: 05-01-2015, 11:54 PM
  5. Replies: 0
    Last Post: 05-08-2014, 01:33 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
 Protected by : ZB BLOCK  &  StopForumSpam