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
I'm going to replace the TCP socket, that is used now to proxy requests from nginx to the application server, by the Unix domain socket on my environment. This approach should be more effective.
However, this enhancement doesn't imply fully replacement, but just a new option. So, it won't break anything neither on Linux, nor Windows.
The text was updated successfully, but these errors were encountered:
Replace a TCP socket used for communication between front-end and
back-end servers with a Unix domain socket to potentially improve
performance a bit.
Remove logging at all. Use redirection from stdout/stderr instead.
Replace a TCP socket, used for communication between front-end and
back-end servers, with a Unix domain socket to potentially improve
performance a bit.
Remove logging at all. Use redirection from stdout/stderr instead.
Replace a TCP socket, used for communication between front-end and
back-end servers, with a Unix domain socket to potentially improve
performance a bit.
Remove logging at all. Use redirection from stdout/stderr instead.
I'm going to replace the TCP socket, that is used now to proxy requests from nginx to the application server, by the Unix domain socket on my environment. This approach should be more effective.
However, this enhancement doesn't imply fully replacement, but just a new option. So, it won't break anything neither on Linux, nor Windows.
The text was updated successfully, but these errors were encountered: