Announcement Announcement Module
Collapse
No announcement yet.
Apache 2 MPM ( Prefork vs Worker ) Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • Apache 2 MPM ( Prefork vs Worker )

    Apache is the world's most widely used Webserver Software. Everyone knows about apache and most of us also have hands on experience with apache. But few of us know that apcahe2 comes with 2 multi processing modules(MPMs)

    1.Prefork

    The prefork MPM uses multiple child processes with one thread each. Each process handles one connection at a time. On many systems, prefork is comparable in speed to worker, but uses more memory.

    Advantages:

    Multiple child processes, 1 thread per child process, child processes handle requests
    Better isolation and stability
    Tested to work correctly with Parallels Plesk
    Developed in Apache 1

    Disadvantages:

    Has higher memory consumption and lower performance over the threaded MPMs

    2.Worker

    The worker MPM uses multiple child processes with many threads each. Each thread handles one connection at a time. Worker is generally a good choice for high-traffic servers because it has a smaller memory footprint than the prefork MPM.

    Advantages:

    Developed in Apache 2 in addition to prefork module
    Multiple processes, many threads per process, threads handle requests
    Uses less memory and provides higher performance

    Disadvantages:

    Does not provide the same level of isolation request-to-request as a process-based MPM does
    If single thread is suspended/out of control, the entire process will be terminated, affecting all of the threads
    Requires a thread-safe processor to handle dynamic content Not supported by Parallels Plesk


    #If you are on linux then run following command to check which MPM is on your machine

    /usr/sbin/apache2 -V | grep MPM
Tag Cloud Tag Cloud Module
Collapse
Working...
X