Notes

First Understand the Problem Apache Is Solving

When users open a website:

Browser → sends request → Apache responds

Simple.

But modern websites keep connections open for a while.

This is called:

Keep-Alive Connection
What is Keep-Alive?

Normally without keep-alive:

Browser requests HTML
Connection closes

Browser requests CSS
Connection closes

Browser requests JS
Connection closes

Creating connections again and again is expensive.

So HTTP introduced:

KeepAlive On

Now:

One connection stays open
Multiple requests reuse same connection

Much faster.

Real-Life Analogy

Without keep-alive:

Customer enters shop
asks one question
leaves

comes again
asks another question
leaves

Very inefficient.

With keep-alive:

Customer stays in shop
asks multiple questions

Better.

Why Keep-Alive Creates a Problem

Here’s the important part.

Suppose user loads website.

Browser may:

download HTML
wait 2 seconds
request image
wait again
request CSS

During waiting:

connection is OPEN
but no real work happening

This idle waiting is the core problem.

Worker MPM Problem

Worker MPM uses:

processes
threads

Each connection occupies:

one thread

Even when client is doing NOTHING.

Example

Suppose:

1000 users connected

But:

only 50 actively downloading
950 idle keep-alive connections

Worker MPM still keeps:

1000 threads busy

because each connection owns a thread.

This wastes RAM and threads.

Event MPM Solves This

Event MPM says:

“Why waste threads for idle clients?”

Instead:

active requests use worker threads
idle keep-alive connections are handled separately

This is the BIG innovation.

Simple Event MPM Flow
Worker MPM
Client connected
↓
Thread stays attached entire time
↓
Even during idle waiting
Event MPM
Client connected
↓
Thread handles request
↓
Connection becomes idle
↓
Thread released back to pool
↓
Special listener watches idle connection
↓
When client sends next request,
a worker thread is assigned again

THAT is the major difference.