glukkkk
commented
1 year ago Our config:
{
"listeners": {
"*:${NGINX_PORT}": {
"pass": "routes"
}
},
"routes": [
{
"match": {
"uri": [
"/swagger/*.yaml"
]
},
"action": {
"share": [
"/var/www/app/$uri"
]
}
},
{
"match": {
"uri": "!/index.php"
},
"action": {
"share": "/var/www/app/public/$uri",
"fallback": {
"pass": "applications/wwwapp"
}
}
}
],
"access_log": {
"path": "/dev/stdout",
"format": "{\"request_method\":\"$method\", \"request_uri\":\"$request_uri\", \"request_time\":$request_time, \"status\":$status, \"remote_addr\":\"$remote_addr\", \"http_user_agent\":\"$header_user_agent\"}"
},
"settings": {
"http": {
"max_body_size": ${NGINX_CONF_MAX_BODY_SIZE},
"send_timeout": ${NGINX_CONF_SEND_TIMEOUT},
"large_header_buffers": ${NGINX_CONF_LARGE_HEADER_BUFFERS},
"large_header_buffer_size": ${NGINX_CONF_LARGE_HEADER_BUFFERS_SIZE}
}
},
"applications": {
"wwwapp": {
"type": "php",
"root": "/var/www/app/public",
"script": "index.php",
"processes": 20,
"options": {
"file": "/etc/php.ini"
}
}
}
}
meezaan
tippexs
We have exactly the same problem as described here: https://github.com/nginx/unit/issues/168.
Our PHP app is based on the Lumen framework. We have a simple route that returns a JSON string of approximately 10MB in size. The script looks really simple:
Then, we start testing it using Siege, an HTTP load tester and benchmarking utility with the concurency number of 50. After 10-20 seconds, the unit:router process starts to consume RAM rapidly. Please take a look at the attached picture. Even after the Siege test is over, the unit:router process still does not free the RAM.
NGINX Unit version: 1.29.1