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
and when we use it, do we always open and then close the connection? or can we leave it until the container is rebooted? I don't quite understand this point.
for example, in my case, I have to monitor a folder on a remote server every five seconds. I don't think it's reasonable to open a connection every 5 seconds
The text was updated successfully, but these errors were encountered:
Opening a new connection every 5 seconds can put a strain on the server and increase latency. Especially if there are many such tasks. On the other hand, long-lived connections can be broken due to timeouts or network problems. It may be worth using a connection pool or one persistent connection with a check for its activity.
There is no need to open a new connection every 5 seconds. Using a Realpath(".") before every command will ensure that the connection is still valid. You should only need to reconnect if it fails.
hi, is there any way to measure connection pools?
and when we use it, do we always open and then close the connection? or can we leave it until the container is rebooted? I don't quite understand this point.
for example, in my case, I have to monitor a folder on a remote server every five seconds. I don't think it's reasonable to open a connection every 5 seconds
The text was updated successfully, but these errors were encountered: