There are a number of MPM modules (Multi-Processing Modules), but by far the most widely used (at least on *nix platforms) are the three main ones: prefork, worker, and event. Essentially, they represent the evolution of the Apache web server, and the different ways that the server has been built to handle HTTP requests within the computing constraints of the time over its long (in software terms) history.
mpm_prefork is.. well.. it's compatible with everything. It spins off a number of child processes for serving requests, and the child processes only serve one request at a time. Because it's got the server process sitting there, ready for action, and not needing to deal with thread marshaling, it's actually faster than the more modern threaded MPMs when you're only dealing with a single request at a time - but concurrent requests suffer, since they're made to wait in line until a server process is free. Additionally, attempting to scale up in the count of prefork child processes, you'll easily suck down some serious RAM.
It's probably not advisable to use prefork unless you need a module that's not thread safe.
Use if: You need modules that break when threads are used, like mod_php. Even then, consider using FastCGI and php-fpm.
Don't use if: Your modules won't break in threading.
mpm_worker uses threading - which is a big help for concurrency. Worker spins off some child processes, which in turn spin off child threads; similar to prefork, some spare threads are kept ready if possible, to service incoming connections. This approach is much kinder on RAM, since the thread count doesn't have a direct bearing on memory use like the server count does in prefork. It also handles concurrency much more easily, since the connections just need to wait for a free thread (which is usually available) instead of a spare server in prefork.
Use if: You're on Apache 2.2, or 2.4 and you're running primarily SSL.
Don't use if: You really can't go wrong, unless you need prefork for compatibility.
However, note that the treads are attached to connections and not requests - which means that a keep-alive connection always keeps a hold of a thread until it's closed (which can be a long time, depending on your configuration). Which is why we have..
mpm_event is very similar to worker, structurally; it's just been moved from 'experimental' to 'stable' status in Apache 2.4. The big difference is that it uses a dedicated thread to deal with the kept-alive connections, and hands requests down to child threads only when a request has actually been made (allowing those threads to free back up immediately after the request is completed). This is great for concurrency of clients that aren't necessarily all active at a time, but make occasional requests, and when the clients might have a long keep-alive timeout.
The exception here is with SSL connections; in that case, it behaves identically to worker (gluing a given connection to a given thread until the connection closes).
Use if: You're on Apache 2.4 and like threads, but you don't like having threads waiting for idle connections. Everyone likes threads!
Don't use if: You're not on Apache 2.4, or you need prefork for compatibility.
In today's world of slowloris, AJAX, and browsers that like to multiplex 6 TCP connections (with keep-alive, of course) to your server, concurrency is an important factor in making your server scale and scale well. Apache's history has tied it down in this regard, and while it's really still not up to par with the likes of nginx or lighttpd in terms of resource usage or scale, it's clear that the development team is working toward building a web server that's still relevant in today's high-request-concurrency world.
Beware: most apache process shares most of its memory with its parents/siblings. You can't easily sum the values of the from apache processes allocated memory. The best what you can do: you start a lot of apache processes and check how this change your allocated memory.
1: StartServers has only a limited importance. It means, how many child process will be started initially. Min/MaxSpareServers are much more important.
2: I can't understand, you didn't said anything your load balancing solution. If you want to be able to handle high traffic, your best option were to use a worker apache (or even an other type of http server) for static file serving, and a prefork-based (I suggest you mpm-itk) for dynamic languages (probably for php). The worker should forward the dynamic requests to the prefork-based server. This structure is also capable to be easily extended to a load-balanced cluster solution.
3: MayRequestPerChild==0 means, that the processes won't ever restarted. Thus if there is a problem with them, it weren't ever fixed, or if they are leaking, this also won't be solved. It can be ok if your system is rock-stable, and you are using only perfect garbage collected languages on the server side (php isn't one of them!), but I think, from practical reasons it is better to use a big integer value (in most cases I use 100 or 500). Beware: a simple child process restart isn't really costly compared to its handling of 100-500 requests.
Best Answer
Stop using prefork module and start using event mpm in apache. Prefork is the old method and moving forward you want to install event mpm.