yespire

Results 6 comments of yespire

@intellent I did my own experiments, sample code is different, but seems consistent with OP observation: ![image](https://user-images.githubusercontent.com/1065882/144427959-00085719-67c9-4224-86d7-55824c998d95.png) after the `$pool->put($pdo);` line, I add a new line in a few different...

@ValiDrv `It doesn't make sense not to have an error/exception if you put back the same connection multiple times` - seems that you and OP agree @intellent `Either way, a...

@NathanFreeman Thank you for the reply ! 1. Could you please elaborate a bit why retain a tiny memory would improve memory management ? 2. What condition(s) would trigger swoole/php...

I use 1 connection with 36k requests, it shows the following output, activity monitor / top shows roughly matching memory footprint, I also tried `gc_mem_caches()` idea, which produced no difference:...

Just want to clarify, the memory creeping issue seems a common theme in node and golang app, so I am not hugely concerned ~ as a periodical or condition triggered...

Run into the same issue Worker: 0 [2023-03-19 03:24:08 $20973.0] WARNING Server::check_worker_exit_status(): worker(pid=5181, id=0) abnormal exit, status=0, signal=11 A bug occurred in Swoole-v5.0.2, please report it. The Swoole developers probably...