You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the example code, you say there is no need to return the connection back as they will be returned when the coroutines are destroyed. I need a clarification here. Here is a sample code. Notice that I have changed the namespace but it is irrelevant at this point:
It's just your example with a sleep() added at the end. And I create 10000 coroutines in a loop exactly 15 times. On each iteration of the outer loop, the memory used raises. This is what I found abnormal. So the question is: Is this the normal behaviour?
Actually, I tried to integrate this library into another Swoole based web framework called Fomo. Interestingly when I benchmark the relevant url, on each benchmark, used memory keeps raising and raising.
The text was updated successfully, but these errors were encountered:
Hello. Thanks for this library.
In the example code, you say there is no need to return the connection back as they will be returned when the coroutines are destroyed. I need a clarification here. Here is a sample code. Notice that I have changed the namespace but it is irrelevant at this point:
It's just your example with a
sleep()
added at the end. And I create 10000 coroutines in a loop exactly 15 times. On each iteration of the outer loop, the memory used raises. This is what I found abnormal. So the question is: Is this the normal behaviour?Actually, I tried to integrate this library into another Swoole based web framework called Fomo. Interestingly when I benchmark the relevant url, on each benchmark, used memory keeps raising and raising.
The text was updated successfully, but these errors were encountered: