Unix socket vs tcp performance. Unix domain socket are similar to system pipes i.

Unix socket vs tcp performance However, there can be also a listening socket. . Which makes sense, considering Unix Domain Sockets end up copying less data and incurr less CPU context switches on most systems. However, Unix domain socket can only be used as "local" IPC. When I ran some basic Redis unix socket benchmarks I found the results quite surprising – unix sockets were 25% faster than TCP sockets for Redis. Building The benchmarks require CMake as well as Google Benchmark . TCP creates a reliable one on one session between a client and server, with full duplex streams of data. PHPで学ぶソケットプログラミング入門 Sep 9, 2017 · Read also about Berkeley sockets API, e. On Linux, it can use either local Unix sockets or remote sockets. in bytes # tcp_rmem and tcp_wmem are per socket Feb 27, 2013 · HTTP Connection. Therefore, I clarify: I am asking about TCP sockets versus Unix named pipes (because MS Windows has another thing called "named pipes", but they seem to be functionally more similar to UNIX domain sockets). Aug 19, 2017 · I am working on an open source package which uses sockets (TCP) to exchange data. Also, the wikipedia article is pretty clear on the following point: "Unix domain sockets may be created as byte streams or as datagram sequences, while pipes are byte streams only. HTTP connection is a higher-level abstraction of a network connection. Also there are benchmarks comparing local unix domain sockets to local TCP sockets which show a significant performance difference. UNIX domain sockets), which based on this, I understand they are a different creature. Note:sockets are in non blocking mode. g O_NONBLOCK) you should use some multiplexing syscall (like . Do a few tests. Moreover, if you wanted a "reliable" exchange you either had to use TCP or design the application to return an ACK. ping-pong latency benchmarks: pipes; unix domain sockets; tcp sockets; throughput benchmarks: pipes; unix domain sockets Mar 3, 2013 · Sockets of course are two way. And the way it transfers data is in first in first out manner, pretty much like FIFO & pipe. Signal sends an integer to another process. sockets, if you need to potentially be able to communicate to different machines ever in the future, choose sockets. Jul 22, 2013 · Today we will go in a different direction on the network stack and benchmark WebSockets vs. I’m testing Percona Server for MySQL 8. Unix domain sockets will give you a bit better performance, while a socket connected to localhost gives you a bit better portability. I used iperf in order to test TCP performance. We only saw maybe about a 20% gain on a generic i5 Linux dual-gigabit system vs. will succeed on read(2) or recv(2) when readable, or on write(2) or send(2) when writable). So based on our non TCP socket vs volume unix socket performance. 2, and now uses a UNIX socket instead of a TCP socket bound on 127. In this comprehensive guide, we will dive into Unix domain sockets, discuss their strengths, […] Jul 9, 2020 · EDIT: I found some comparisons here, but these are UNIX-sockets (a. With Unix domain sockets, a server has to set up one unix domain socket and go through all the networking business. For unix domain socket the number is always 219264,but for TCP this number is much higher. Update: Since this answer was posted the . Socket can handle more than one peer. What I'm trying to accomplish is setting up docker-compose to build an php-fpm, nginx and mysql containers and set up nginx to use fastcgi_pass to php-fpm via unix socket instead of TCP. TCP sockets also have configurable buffer sizes while Unix sockets have a fixed buffer size, so TCP socket buffers can get much deeper. Oct 30, 2015 · For example, TCP on Linux-on-HyperV can get 30Gbps and on Linux-on-Azure can get 20G+. May 26, 2017 · As you say it's just a wrapper over the Socket class so there is no performance difference between them it's purely a style choice. Aug 5, 2014 · If latencies are crucial, I'd switch to UNIX domain sockets (very similar to TCP sockets) or pipes (faster, but more complicated, you need two pipes for a bidirectional connection). localhost: We posted a lot of tuning advice on this blog already. Nov 28, 2016 · @SatoKatsura Not certain, but there's some difference based on what I've read even if it's not night and day different. Jan 20, 2010 · Both are inter process communication (IPC) mechanisms. But I prefer TCP since socket can give you some headaches. Shared memory (SHM) is a piece of memory where you can put data and share this between processes. Two programs can just open a FIFO and then they are talking. //I think for Windows VM, it is similar; also on other virt platform such XEN, KVM, TCP did even better. Jan 5, 2017 · so. Dec 27, 2023 · Inter-process communication (IPC) between applications running on the same Linux machine is vital for building scalable, high-performance systems. However, they are essential for remote access. A socket is an endpoint of a distributed communicating machine that uses sockets to implement the client-server model and solve different network applications. Based on my admittedly very amateur benchmarks with the redis-benchmark and pgbench tools I saw a very surprisingly high 32% improvement for Redis and a modest 10% improvement with Postgres. It seems slightly more complicated to use two variables instead of one (that is, two pipes instead of one socket). I've found the following pages helpful - IPC performance: Named Pipe vs Socket (in particular) and Sockets vs named pipes for local IPC on Windows?. In particular, zeromq is a great library and should probably be performing better, especially because we are only using the TCP implementat Jan 10, 2021 · What are the differences from running PHP-FPM over an Unix Socket vs a TCP/IP Socket? Performance Analysis of Various Mechanisms for Inter-process Communication. With HTTP connection the implementation takes care of all these higher-level details and simply send HTTP request (some header information) and receive HTTP response from the server. They carry less baggage than TCP sockets and offer lower latencies. It sounds like the concensus is that shared memory is the way to go if you're really concerned about performance, but if the current system you have is a message queue it might be a rather Aug 24, 2024 · Unix sockets provide a powerful IPC mechanism for building robust containerized applications. a c libpcap implementation. As per best practices, each of my "pods" are multiple docker containers that are supposed to live together on the same machine/host. from publication: XenSocket: A High-Throughput Interdomain Transport for Virtual May 13, 2016 · Unix sockets vs. As I understand it, at least on linux TCP/IP sockets always result in the generation and decoding of TCP/IP packets, even if the client and server are on the same machine. but we're thinking about writing our own implementation that on same server processes will communicate on unix sockets, and between servers that will communicate using tcp. Documentation. Sep 17, 2013 · And surely all operating systems rely on high performance TCP/IP so much that it cannot be significantly slower than Unix sockets - Linux does all sort of zero-copy tricks even for network traffic, so it surely must be fast for loopback. 1 (the latter being prone to cross-site request forgery attacks if you happen to run Docker directly on your local machine, outside of a VM). Doesn't mesh well with multi-threads Apr 30, 2015 · So its less a performance issue and more a question of what you want to capture. How to detect and measure the impact May 23, 2011 · TCP and UDP are different facilities under IP, but UNIX sockets are local to the host and simpler, like pipes. Aug 27, 2020 · The proper name for unix sockets is Unix Domain Sockets, because they all reside within one computer. INETドメインとUNIXドメイン. Edit: raw packets can be either IP level (AF_INET) or data link layer (AF_PACKET), pcap might actually use raw sockets, see Does libpcap use raw sockets underneath Oct 18, 2016 · Unix sockets operate at a lower level OSI model layer than TCP sockets so they should be faster. For fast, efficient IPC, Unix domain sockets (sometimes called IPC sockets) are an excellent choice compared to TCP sockets and other IPC methods. Feb 20, 2013 · Depending on the platform, unix domain sockets can achieve around 50% more throughput than the TCP/IP loopback (on Linux for instance). B sends some other packets to A in 5 seconds intervals. Some very crude IPC benchmarks. Jul 8, 2009 · I know that, since this is Linux, the socket handle is simply a file descriptor, and therefore it is valid to perform read() and write() calls on the socket, however the sockets API also provides the send() and recv() functions to perform the same tasks. Apr 13, 2020 · I have not looked at this topic in years, so let’s see how a modern MySQL version does on relatively modern hardware and modern Linux. Sep 11, 2023 · In my experience, for small unbatchable messages, UNIX sockets are fast enough not to warrant the complexity of dealing with shared memory. In fact, we only saw about 80%-150% vs. 1:9000;). Jul 25, 2017 · I am running a nginx server to serve by PHP website in Alpine Linux. com UNIX domain sockets should offer better performance than TCP sockets over loopback interface (less copying of data, fewer context switches). 3 megabytes/sec on this machine, this example really just proves Doug's other point: the difference between a Unix socket and a TCP socket is unlikely to be important for Postgres purposes, because it'll be swamped by other factors. So make a long answer short: Yes, there is a performance difference, sockets are faster. Compared to TCP sockets, Unix sockets offer improved performance and security, especially in Docker I have worked with Unix sockets between machines (not domain) and I remember that making and breaking the connection would cause sockets to linger awhile before they finally went away. In TCP a socket is defined by the elements of a TCP connection between two processes (IPAddress1, Port1, IPAddress2, Port2). I know that with Unix sockets can be useful only if you're on the same server. A client creates a temporary unix domain socket of its own and connects to the servers socket. Unix domain; Berkeley; TCP; Internet; One of the things the book said is that if you want to communicate between remote hosts, you couldn't use Unix domain sockets because they are for IPC on the same host. socket(7) on Linux. This is a socket that a allows a process to listen for connections established from other processes through the network. Jun 4, 2012 · Winsock is smart enough to know if it's talking to a socket on the same host and, in that case, it will short-circuit pretty much everything below IP and copy data directly buffer-to-buffer. These sockets can be stream-based or datagram-based. May 15, 2013 · Yes, Unix domain socket is kind of socket, so it's API is similar to other socket APIs such as TCP or UDP, etc. Long story short, I set-up unix sockets between my Nextcloud container, the Postgres database and the Redis container. Why you should consider UDS and named pipe? Both Unix domain socket and Named pipe (AKA fifos) offer better performance than TCP/IP because they can avoid the networking overhead. He demonstrated a specific case of a 2x performance degradation while using TCP/IP connection. they only send data without checksums or other meta information, contrary to TCP/IP sockets that use a three-way handshake; in other words data carried over Unix sockets doesn't have to through the TCP/IP layers For exchanging messages between threads/processes, it compares using domain sockets vs UDP multicast, for various data sizes. 1")? Do any Linux operating systems optimize the latter into the former or will using AF_INET always carry the TCP/IP overheads? On Thu, Jan 25, 2001 at 11:07:19PM -0500, Tom Lane wrote: > Frank Joerdens <[EMAIL PROTECTED]> writes: > > What performance penalty can I expect when going over TCP/IP sockets > > instead of Unix sockets? > > On a properly designed kernel, there shouldn't be any measurable > performance difference between a local TCP connection and a Unix Sep 3, 2019 · For the caller, the behavior is the same. Aug 23, 2020 · Unix & Linux: Performance of unix sockets vs TCP portsHelpful? Please support me on Patreon: https://www. IP sockets (especially TCP/IP sockets) are a mechanism allowing communication between processes over the network. poll(2) or the older and obsolete select(2)) to ensure that your socket is indeed readable or writable (i. So naturally using TCP sockets will be less heavy than using HTTP. 5. The default behavior of redis-benchmark is to use the TCP/IP loopback. Jan 11, 2013 · I was always running Nginx in combination with PHP-FPM listening via TCP/IP (fastcgi_pass 127. Running both of these commands should show that for 1k packets repeated 100,000 times, Unix domain sockets beat localhost TCP sockets by about 3x. Feb 1, 2013 · As for TCP you can measure its performance youself . When I compare the performance of local sockets to remote over local loopback, I find Unix sockets to be 50x faster. Mar 30, 2015 · Quote from Performance: TCP loopback connection vs Unix Domain Socket: When the server and client benchmark programs run on the same box, both the TCP/IP loopback and unix domain sockets can be used. As a result, it is much easier to regulate which users have access to a UNIX domain socket than it is for a TCP socket; And simply one another benefit comes from UDS definition: Mar 18, 2024 · It helps to identify a process. Apr 13, 2020 · In order to measure the throughput and speed of a unix socket you can use socat, "multipurpose relay for bidirectional data transfer". Mar 18, 2024 · Unix sockets, also known as Inter-process Communication (IPC) sockets, are data communication endpoints that allow bidirectional data exchange between processes running on the same computer. UNIX domain sockets are uses for communication between processes on one host similar as TCP-Sockets are used between different hosts. Your numbers show it. Now we thought we would take it a step further and share some more advice and common “mistakes” that we see people making when configuring web applications. Set the length of buffer to read or write and run iperf in server mode and also run a few iperf processes in client mode. In general, we use two major communication modes in socket programming: a non-connected UDP mode and a connected TCP mode. (Though I have validated Re: [GENERAL] Performance: Unix sockets vs. Unix Sockets, also known as Unix Domain Sockets, are a method of inter-process communication (IPC) that allows data exchange between processes running on the same host. py Jun 23, 2015 · Socket and Unix Domain Socket. The slightly longer version is that writing TCP sockets can be hard, there's a lot of things that are easy to have problems with, but 0MQ guarantees the message will be delivered in its entirety. As per the linux man page; Socat is a command line based utility that establishes two bidirectional byte streams and transfers data between them. I would flip it around and say that WebSockets is an encapsulation of TCP that brings TCP like functionality and performance to browsers without using a plugin and without giving up hard-won browser security best practices (like CORS). In your case, looks like there is a mismatch between 2 values. In our scenario, we have a variable number of worker processes in a single server. " May 7, 2015 · PostgreSQL will use TCP/IP loopback (if you specify localhost, otherwise if you specify nothing, it will use Unix domain socket. If performance is the only thing you care about then plain TCP is the best solution for you. So is there any legitimate reason for using Unix sockets here, or is it just some weird historical accident? Dec 19, 2012 · I know that STREAM sockets use TCP, Datagram sockets use UDP and all the TCP,UDP stuff, packets arriving in order, ACK, NACK etc. ), then one infinite loop starts to send 256kB sized packets with the client socket to the server socket. Remote procedure calls are a programming technique (often using socket(2) system call on Linux). Dec 19, 2024 · TCP loopback connection vs Unix Domain Socket performance - Stack Overflow: [invalid URL removed] PostgreSQLのUNIXドメインソケットとTCPソケットのプログラミング例 PostgreSQLへの接続には、UNIXドメインソケットとTCPソケットの2つの方法があります。 I am reading The Linux Programming Interface and it describes several different types of socket used on Linux:. Python dpkt/scapy implementation. Aug 12, 2019 · I am comparing how many bytes a send call can transfer when a socket is tcp and when it is unix socket. Why is this difference? Both the programs are executed in the same machine. Signal. Unix Domain Sockets are not routable, so they are not accessible from the outside, so they are usually considered safer than TCP for local communication. unix - sockets for local interprocess communication. listen = '/tmp/php-fpm. Call socket(2). There's no message boundary for TCP. If you are not suffering high server load, just choose what fits Nov 28, 2023 · Both Unix domain socket and Named pipe (AKA fifos) offer better performance than TCP/IP because they can avoid the networking overhead. > Of course, since the kernel is certainly capable of net socket > throughput well in excess of 0. Feb 25, 2005 · The sockets layer provides a reasonable abstraction of communications services, so it's not hard to write an application so that the connection/binding portion knows about TCP and UNIX domain sockets, and all the rest just uses the socket it's given. For example, if you do a "git pull" in a way that changes the folders permissions write/read/execute, maybe nginx cannot access socket. WebSockets are not similar to HTTP. The distributed communication Oct 30, 2009 · As for TCP performance, I have done this sort of test recently on an HP-UX server (8 Intel Itanium 2 processors 1. h. I see that nginx can connect to php-fpm process via either unix socket or host:port. 19 running on Ubuntu 18. Bruce Momjian, of the PostgreSQL project, ran some numbers and saw a 30% improvement using Unix Sockets over a TCP/IP loopback. 3 megabytes/sec on this machine, this > example really just proves Doug's other point: the difference between a > Unix socket and a TCP socket is unlikely to be important for Postgres > purposes, because it'll be swamped by other factors. Other Scenarios Second question: is there a significant performance difference between using a socket with a AF_UNIX domain vs a socket with a AF_INET domain and the loopback address ("127. The full benchmark analysis is run with: python run. Can be used for different protocol. You can use any of TCP/IP or Unix-Socket as long as nginx and php5-fpm values match. The HTTP-compatible handshake is just to allow WebSocket connection on the same port that a webserver is running on (so the webserver can forward them), but once the connection is established, the webserver is not in the loop. See sys/msg. My purpose is to send data packets containing few integer values in frequent intervals (around 50 ms) from process A to B. To avoid routing effects, server and client are Jul 12, 2021 · This question is similar to IPC performance: Named Pipe vs Socket but focusses on anonymous instead of named pipes: How is the performance difference between an anonymous pipe and a TCP connection on Mar 19, 2007 · If I use sockets for IPC, and can easily distribute my applications. When I create a UNIX domain socket which is a local socket, how would it matter if the socket is STREAM socket or DATAGRAM socket? Sep 5, 2018 · The case is very simple, one TCP Socket listens on localhost, another TCP Socket connects to the listening socket (from the same program, on the same machine oc. Socket can be stream or datagram, pipe/fifo are always streams. Depending on the platform, unix domain sockets can achieve around 50% more throughput than the TCP/IP loopback (on Linux for instance). Sep 5, 2017 · Socket is bi-directional, pipe/fifo is uni-directional. In a sense, sockets are a network that is entirely contained within the kernel; rather than using network interfaces to send data, that same data can be sent directly between programs. Sep 13, 2014 · Here is one discussion: UNIX Domain sockets vs Shared Memory (Mapped File) I can add that sockets are very primitive, just a stream of bytes for stream sockets. 04 on a Dual Socket 28 Core/56 Threads Server. May 4, 2018 · I would like to know which IPC gives more performance in linux (TCP IP socket vs message queue). They are normal sockets with some framing and an HTTP-compatible handshake. Jun 5, 2013 · @MarcCasavant the way you ask the question seems to imply that WebSockets is overhead with no good reason to exist. Jul 7, 2015 · Unix Domain Sockets make nginx faster to communicate with php-fpm, and use less resource, because TCP has an overhead, as protocol, over Unix sockets, even on the loopback. At my last role we benchmarked TCP sockets vs Unix sockets in a variety of scenarios. Every RPC request expects exactly one reply and is software initiated. Net source code has become available. UNIX Domain Sockets These are a faster and more efficient way to communicate with the server when both the client and server reside on the same machine. Nginx) and php-fpm are in the same box and You have the option to scale horizontally both the front and back-end together (say you are building a container with both and you can create more containers, each with a working pair) or A listening TCP socket is identified by local port and possibly local IP. See full list on baeldung. Sep 29, 2013 · Particularily if you use non-blocking I/O (e. Meant for network communication, but can be used locally too. Jul 16, 2021 · Benchmarking UDS vs loop-back TCP sockets Redis. k. Then I tried to let it listen to a Unix Socket instead (fastcgi_pass unix:fastcgi. Note that different endpoints of a socket can share the same IP address; however, they must listen on different TCP / UDP ports to do so. They provide an efficient and reliable way for applications to communicate, bypassing the complexities of networking protocols. However, for bigger and/or batchable messages, shared memory ringbuffer + UNIX socket for synchronization is the most convenient yet fast IPC I've used. You can easily move the server app to another OS by just changing the IP address from localhost to a different hostname. The caller may not even know anything about datagrams (it may not know that this is a socket and not a file, it may not know that this is a datagram socket and not a stream socket). e. – Using a socket (e. Of course, since the kernel is certainly capable of net socket throughput well in excess of 0. 0. It does indeed show that TcpClient is a very light wrapper over the Socket class which is itself a wrapper on top of the native Sep 2, 2013 · sockets packetize communication using IPv4 or IPv6; that communication can extend beyond localhost. In terms of named pipes vs. a. TCP/IP sockets Adrian Phillips Fri, 26 Jan 2001 08:52:13 -0800 >>>>> "Frank" == Frank Joerdens <[EMAIL PROTECTED]> writes: Frank> On Thu, Jan 25, 2001 at 11:07:19PM -0500, Tom Lane wrote: >> Frank Joerdens <[EMAIL PROTECTED]> writes: > What performance >> penalty can I expect when going over TCP/IP May 15, 2019 · Security: UNIX domain sockets are subject to file system permissions, while TCP sockets are not. Even though the latter combination is often recommended for being generally faster, I do not see any significant boost in performance. SOCK_STREAM), so the answer isn’t related to how TCP performs in comparison to another transport protocol like UDP, for instance (see update 1). May 15, 2017 · For this reason, the REST API endpoint (used by the Docker CLI to communicate with the Docker daemon) changed in Docker 0. Message Queue. Are there any practical and/or theoretical Mar 18, 2024 · Unix Sockets TCP/IP Sockets; Full Name: Unix sockets are also known as Inter-process Communication (IPC) sockets: TCP/IP stands for Transmission Control Protocol/Internet Protocol: Functionality: Unix sockets are used for communication between processes running on the same computer: TCP/IP sockets are used for programs running on different Dec 21, 2024 · Performance Can be slower than UNIX domain sockets for local connections due to the overhead of the TCP/IP stack. Jul 20, 2023 · Meanwhile, Hans-Jürgen Schönig’s presentation, which brought up the old discussion of Unix socket vs. regular old TCP sockets, all on the JVM. Socket and fifo do not require related processes, whereas unnamed pipes do. Nov 12, 2013 · In my experience, socket and TCP performance is almost identical. Jan 27, 2012 · Well, the short version is give it a try. 5 GHz 6 MB, 400 MT/s bus) and on Red Hat Linux (2 IA-64 1,6 Ghz). I understand the importance of these over internet. Download scientific diagram | Performance Comparison of TCP vs. This may actually be an advantage - it tends to make messages between different subsystems small and simple, promoting lean interfaces and loose coupling. Usage: Use pipes: when you want to read / write data as a file within a specific server. Unix domain socket are similar to system pipes i. checked the buffer size,these are the Mar 27, 2008 · Compared to FIFO's, Unix domain sockets are a minor nightmare to use. Jan 21, 2021 · In your opinion what are the pros and cons of the two solutions? Here's what comes to my mind: TCP/IP Socket with two containers PRO better scalability different services on different containers are How to tune the Linux kernel TCP performance to optimize data center NFS performance and other network services. That the datagram stays pending is implicit knowledge about how IP stacks work in kernels and not visible to the caller. com/roelvandepaarWith thanks & praise to Go Aug 2, 2019 · I'm wondering how Docker manages a unix socket when it's shared across containers and how it affects the performance compared to just using TCP. Benchmarking TCP/IP Connection vs Unix Domain Socket for MySQL. A unix domain socket (sometimes shortened to unix socket) on the other hand operates on a single Sep 11, 2023 · TCP Buffer autotune having problems also matters at certain scale, but in my experience requires a tipping point. HTTP is a layer built ontop of the TCP layer to some what standardize data transmission. sock') makes sense when both the front-end (e. However the difference tends to decrease if you make good use of pipelining. Unix Domain Sockets as a Function of Message Size. This may all seem quite academic, after all WebSockets is made Jan 15, 2014 · Unix domain sockets can achieve around 50% more throughput than TCP sockets (as stated in the official Redis documentation) but this also depends on the platform. If performance is your main issue search for PF_RING etc, that's what current IDS use for capturing. When the server and client benchmark programs run on the same box, both the TCP/IP loopback and unix domain sockets can be used. Sockets are often also used for asynchronous messages (for example, the X11 protocols stack, WebSockets, SMTP). from publication: Xensocket: A high throughput interdomain transport for vms Sep 18, 2015 · I have implemented a small benchmark for socket communication via TCP and UDP in Python. As I understand it, Message Queues still incur system call overhead, just like socket calls. I'm currently using Kubernetes to manage my cluster and my containers. my raw options are tcp or unix sockets. Managing ports and firewalls is a nightmare. Jan 3, 2017 · It’s important to notice that both IP and Unix socket implementations are using TCP (socket. OS maintains discrete message. patreon. – Dec 21, 2017 · On a very modest but much beefier test system with an Intel Celeron J1900 and I211 Gigabit controllers it drops to about 50%-100% vs c libpcap. Surprisingly, TCP is almost exactly double as fast as UDP. Bidirectional. HTTP connection is a protocol that runs on a socket. There are lot of tools to measure: iPerf, ntttcp (Windows), ntttcp-for-Linux, netperf, etc: Download scientific diagram | Performance Comparison of TCP vs. Taken from ServerFault (What's the difference between Unix socket and TCP/IP socket): A UNIX socket is an inter-process communication mechanism that allows bidirectional data exchange between processes running on the same machine. What advantage does a UNIX Message Queue provide versus a TCP or UDP Socket, and when should they be used? Aug 23, 2020 · Unix & Linux: Performance of unix sockets vs TCP portsHelpful? Please support me on Patreon: https://www. socket;). What happens is that when Unix sockets are used, the entire IP stack from the operating system will be You need to find out if your system is under heavy load so that a socket is a must or you can focus on a nice system design (separating services), then a tcp/ip solution would be better. Everything else is identical. With less work, comes better performance. g. UNIX Message Queues are local to the processor. Nov 28, 2023 · For local calls via gRPC, we have better choices for transports than TCP/IP: Unix domain socket and Named pipe. NOTE: The code is rather old and there might be sub-optimal configurations!We are happy to update the configuration with concrete suggestions (see contributions below). TCP/IP connection, triggered me to write about other aspects of network impact on performance. zwsxtzl aotr swhjo bivfuo gxojw bwdwwwul jhfrv hxpesp cpsehyh mveu