Keep Server Online
If you find the Apache Lounge, the downloads and overall help useful, please express your satisfaction with a donation.
or
A donation makes a contribution towards the costs, the time and effort that's going in this site and building.
Thank You! Steffen
Your donations will help to keep this site alive and well, and continuing building binaries. Apache Lounge is not sponsored.
| |
|
 Topic: ThreadsPerChild vs ServerLimit to increase capacity? |
|
| Author |
|
kmizser
Joined: 24 Aug 2016
Posts: 1
Location: Los Angeles, CA
|
 Posted: Wed 24 Aug '16 22:22 Post subject: ThreadsPerChild vs ServerLimit to increase capacity? |
 |
|
I'm looking for some tuning guidelines...
Assuming default(ish) Apache mpm_worker_module numbers:
ServerLimit 16
StartServers 2
MaxClients 400
MinSpareThreads 25
MaxSpareThreads 75
ThreadsPerChild 25
This would allow 25 (threads) x 16 (processes) = 400 maximum concurrent connections. It would create maximum of 16 apache processes with 25 thread capacity each.
Now if I want to support 800 maximum connections I have 2 options:
1. Double ServerLimit to 32
2. Double ThreadsPerChild to 50
- Are their any guidelines on which parameter to adjust?
- What are the pros and cons of increasing each parameter?
- Are the answers different on a 4-core vs 16-core machine?
- Are the answers different on a physical machine vs virtual instance?
- What if I want to increase capacity 10-fold to 4000? ServerLimit to 160 -or- ThreadsPerChild to 250 -or- some kind of a combination of both?
This is assuming Apache 2.2.31 on RedHat Linux 6.8.
I'd appreciate any help on this. |
|
| Back to top |
|
|
|
|
|
|
