How realistic is this benchmark? Before people start pulling out pitchforks from their basements (sheds, whatever) – I do realize this is a rather NOT a realistic test-case scenario. In the real life scenario, it is somewhat unlikely your API will just be serving some static json responses without any io calls. And even a … Read more
There are many reasons why you may want to use reverse proxy in front of your application – (such as mezzio php framework with swoole/openswoole). Reasons to use nginx with your php+swoole/openswoole applications: efficient serving of static assets – while swoole will serve it very efficiently, but it will never beat raw compiled performance of … Read more
One issue Ive ran into recently: Swoole and Openswoole use urlencode to encode cookies when one invokes Swoole\Http\Response->cookie() method instead of rawurlencode. While swoole offers an alternative in form of rawCookie ( and then you could encode value as you wish) – not all depnedent frameworks and libraries support that: https://openswoole.com/docs/modules/swoole-http-response-cookie Some popular PHP libraries … Read more
I’ve recently ran into this error message with mezzio/swoole – which would popup for every hot reload on code change. Ive tried couple of different things (completely on the hunch) like: disabling ticks (this didn’t help) disabling side swoole processes (this didn’t help) raising max_wait_time to 60 seconds (this didn’t help) checking mysql/redis connection pools … Read more
I’m a huge fan of swoole/openswoole for php as It solves a lot of hard scalability problems for us that is hard to solve otherwise in php. One of these problems is connection pooling. Why use connection pools for your redis or mysql connections? – but for speed of course! it takes relatively significant amount … Read more
