Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: Performance: Unix sockets vs. TCP/IP sockets
- From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
- To: Frank Joerdens <frank(at)joerdens(dot)de>
- Cc: pgsql-general(at)postgresql(dot)org
- Subject: Re: Performance: Unix sockets vs. TCP/IP sockets
- Date: Thu, 25 Jan 2001 23:07:19 -0500
- Message-id: <28501.980482039@sss.pgh.pa.us> <text/plain>
Frank Joerdens <frank(at)joerdens(dot)de> 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-socket connection. There are not-so-well-designed kernels out there, but I forget which they are (and you didn't bother to specify your platform anyway). If you want a reliable answer, fire up a data-transfer-intensive task, say a COPY OUT of a large table, and time it both ways. regards, tom lane
- Follow-Ups:
- Re: Performance: Unix sockets vs. TCP/IP sockets
- From: Frank Joerdens
- Re: Performance: Unix sockets vs. TCP/IP sockets
- References:
- Performance: Unix sockets vs. TCP/IP sockets
- From: Frank Joerdens
- Performance: Unix sockets vs. TCP/IP sockets
- Prev by Date: DBD::Pg using int2 / smallint
- Next by Date: Re: PL/PySQL?
- Previous by thread: Performance: Unix sockets vs. TCP/IP sockets
- Next by thread: Re: Performance: Unix sockets vs. TCP/IP sockets
- Indexes: