Sujet : Re: Are We Back to the "Wars" Now ?
De : vallor (at) *nospam* cultnix.org (vallor)
Groupes : comp.os.linux.miscDate : 22. Nov 2024, 07:09:05
Autres entêtes
Message-ID : <lqalg1F7fi9U2@mid.individual.net>
References : 1 2 3 4 5 6 7 8 9 10
User-Agent : Pan/0.161 (Hmm2; be402cc9; Linux-6.12.0)
On Fri, 22 Nov 2024 03:12:43 -0000 (UTC), Lawrence D'Oliveiro
<
ldo@nz.invalid> wrote in <
vhosra$1171f$1@dont-email.me>:
On Thu, 21 Nov 2024 21:55:37 -0500, Phillip Frabott wrote:
We had to drop named pipes solely because of the performance hit
because it is writing to a file system so it's being controlled by the
file system, even if that file system is in memory.
That doesn’t make any sense, if we were talking about Linux. Is this on
Windows, by any chance?
Doesn't the named pipe connection work through the filesystem code?
That could add overhead.
Can't use named pipes on just any filesystem -- won't work on NFS
for example, unless I'm mistaken.
As the demand grows, we are actually at the limits of performance that
even unnamed pipes gives us. So we are starting to migrate to UNIX
sockets which has about double to bandwidth and performance of pipes.
Not sure how that works, given that Unix sockets are actually a more
complex mechanism than pipes.
With Unix sockets, once the connection is made, it's all in-memory
networking. I suspect (but don't know) that named pipes require the
data to pass through the filesystem for each write.
But I could be completely wrong, don't take my word for it.
-- -v System76 Thelio Mega v1.1 x86_64 NVIDIA RTX 3090 Ti OS: Linux 6.12.0 Release: Mint 21.3 Mem: 258G "The way to a man's heart is through the left ventricle."