Please read Readme for the basic benchmark result.
Potential memory leak might still exist in Swoole. The reason is still unknown, but there's a max_request config in Swoole for solving this problem. Each worker will restart gracefully after handling the number of max_request to prevent from memory leak.
All 3 comments
Hi @hakuno ,
Please read Readme for the basic benchmark result.
Potential memory leak might still exist in Swoole. The reason is still unknown, but there's a max_request config in Swoole for solving this problem. Each worker will restart gracefully after handling the number of max_request to prevent from memory leak.
Most helpful comment
Hi @hakuno ,
max_requestconfig in Swoole for solving this problem. Each worker will restart gracefully after handling the number ofmax_requestto prevent from memory leak.