Mamp - apache forces cpu 100% usage

[cool11]

I use mamp as web server in my mbp c2d.
The problem is that after some time of using, it starts to push the cpu usage to 95-98%!

I look at 'activity monitor' application of mac os x and I can see about 10 httpd processes!
Only 1 mysql process.

I have heard that mac os x has pre-installed apache. Is this the problem?

What do you suggest?
Is it normal to have 10 httpd processes? Is it the mac os x apache? Is it a bug of mamp?
How can I solve it?

[cool11]

I am working on it.
I just closed mamp. All httpd processes gone.

What is going on?

[ChrisA]

I
I look at 'activity monitor' application of mac os x and I can see about 10 httpd processes!

There is a config line that controls how many httpd processes are created. It's in httpd.conf. "10" is a reasonable number for a medium sized server. 1 or 2 might be better for a low volume server. Having these already running avoids the time it takes to start a new process so Apache can handle a HTTP request without the startup delay.

Remember Mac OS X uses "copy on write" for process images so having 10 in memory does not take up much more room then having only 1 in memory. The same physical RAM is used in multiple processes.

Why the 100% CPU? Need more info.

[cool11]

All I wanna do is test and run a site I design, offline. Sometimes I have safari, firefox, opera open simultaneously to test the site. Thats all. We don't speak about a real time server serving hundreds or thousand of users.
Mamp is well-known in mac web development world.

I would not have made this post if I did not heard my mbp having the fans fully working when I use mamp. I can also see the 2 cpu usage meters in the bar going to 100%. This is also checked with activity monitor.

All these httpd processes do a heavy task for mbp.

It is not logical. That should not happen, I suppose.

Just running mamp and the cpus pushed to 100% usage.

What else should I say?