No. The main problem the event MPM addresses is HTTP keep-alive. With pre-fork and threaded, every connection takes up a process or thread. This sucks for keep

No. The main problem the event MPM addresses is HTTP keep-alive. With pre-fork and threaded, every connection takes up a process or thread. This sucks for keep-alive because it can take a while before the client issues the next request. The event MPM puts that idle connection in a kqueue/epoll/etc. pollset and recycles the process/thread for another request. It's a conceptually simple change but it has some profound performance implications.