I understand that support with event is limited and noticed that there has been work to make it work better with it. We are currently using Apache 2.4.57 + event with mod_qos 11.70. When we test with 11.74 we are noticing increased memory usage by the parent httpd proc. We are not seeing same behavior if we use worker with 11.74
it more than doubles the amount of memory used. These are very dense servers with lots of vhosts + ssl so base memory usage is kinda high but with latest version of mod_qos seems to be a lot worse. If it makes any difference only mod_qos directive we are using is QS_LocRequestLimitDefault
Last edit: Gabriel Pineda 2023-07-25
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi
mod_qos changed how it calculates the maximum number of connections. As you don't use any connection based limitations, you can override the default by using the QS_MaxClients directive (to the same value as you have set for MaxRequestWorkers).
Hope this helps...
Regards, Pascal
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I understand that support with event is limited and noticed that there has been work to make it work better with it. We are currently using Apache 2.4.57 + event with mod_qos 11.70. When we test with 11.74 we are noticing increased memory usage by the parent httpd proc. We are not seeing same behavior if we use worker with 11.74
vs
it more than doubles the amount of memory used. These are very dense servers with lots of vhosts + ssl so base memory usage is kinda high but with latest version of mod_qos seems to be a lot worse. If it makes any difference only mod_qos directive we are using is QS_LocRequestLimitDefault
Last edit: Gabriel Pineda 2023-07-25
Hi
mod_qos changed how it calculates the maximum number of connections. As you don't use any connection based limitations, you can override the default by using the
QS_MaxClientsdirective (to the same value as you have set forMaxRequestWorkers).Hope this helps...
Regards, Pascal