[Subsentient]

Write your own. Wrote one fairly recently in good-ole-sepples that uses UNIX domain sockets and pushes around half a gigabyte a second on weak ARM hardware. Domain sockets are great. Shared memory is even better. If you need a portable solution between processes, not threads, I recommend domain sockets and a simple binary protocol for high throughput.

[nsteel]

The article mentions that the perf of unix domain sockets was not significantly better:

> I was surprised at how similarly most things performed. I did a cursory investigation into Linux-specific approaches like dbus and Unix Domain Sockets, but they seemed to be in the same ballpark as the non-shared memory approaches.

[infamouscow]

I wholeheartedly agree. To add a bit more carrot for people on the fence, unlike TCP/UDP sockets, you don't have to be concerned about endianness because the bits never leave the machine. For a lot of use-cases, this is a big win that doesn't get as much appreciation as I think it should.

[kouteiheika]

> unlike TCP/UDP sockets, you don't have to be concerned about endianness because the bits never leave the machine

Why would you be concerned about endianness even if you're using TCP or UDP, if you control the protocol?

Little endian won; in 99.9% of cases there's no reason to use big endian unless you're implementing an existing protocol which explicitly mandates big endian. Doing something over the network doesn't magically make it better to use big endian, and the whole "network endian = big endian" is just silly.

[01HNNWZ0MV43FF]

I just use little endian everywhere. I figure unit tests will catch it if I screw up

[rkangel]

This is reasonable, but a bit unfortunate specifically for TCP/UDP. The extremely strong convention is that all network protocols are "network byte format" which is Big-Endian.

Obviously no issue for local IPC, but when things become published network protocols, little-endian makes me sad.

[0x457]

> This is reasonable, but a bit unfortunate specifically for TCP/UDP. The extremely strong convention is that all network protocols are "network byte format" which is Big-Endian.

This is really only relevant for packet headers, tho. What goes into payload is entirely up to the developer. There is no specific reason to keep endianness the same between TCP/UDP and its payload. As long as it's clear which one to use.

RFC1700 is marked as obsolete. IIRC, network order is big-endian is because it allowed faster packet switching? But we're at the point where I can do dual-border routing with DPI orders of magnitude faster than switches from that era can do basic switching.

Some people choose little-endian for payload because they are:

a) unaware of endianness and will discover a funny thing when they suddenly start talking between BE and LE nodes. Rust forces you to choose when you write or read numbers.

b) Think since their CPU is LE then payload should be LE as well for performance. This is false because even on ancient hardware this would not take more than 3 cycles (in a context of network communication shaving off 3 cycles is a hilarious endeavor)

c) Aware of all of this and choose LE because they felt like it.

[gpderetta]

> Think since their CPU is LE then payload should be LE as well for performance. This is false because even on ancient hardware this would not take more than 3 cycles (in a context of network communication shaving off 3 cycles is a hilarious endeavor)

Having to do BE/LE conversions means that you can't just reinterpret cast your network buffers into whatever is the native application message type. Yes, there are ways around that (by wrapping every integer field with an endian converting accessor), but it is a significant amount of yak shaving.

[0x457]

Well, the native application type depends on what platform that application is running. That means LE in 99.9% of cases. Don't need to sell LE for payload to me, I'm already sold. It's people that think network byte order has anything to do with payload that are confused.

[01HNNWZ0MV43FF]

Yeah I like the idea that my code could compile down to memcpy, even though maybe the compiler may not choose to do it

[parhamn]

A named pipe (fifo) would be an interest to test too. I believe theyre a good bit faster than a unix socket.

[i80and]

My recollection from Advanced Programming in the Unix Environment is that unix sockets are actually often faster than named pipes:

You got me curious; according to a quick search, that seems to hold up according to this more recent post (which doesn't note the OS, annoyingly):

https://www.yanxurui.cc/posts/server/2023-11-28-benchmark-tc...

I'd be interested in more robust data here.

[novafacing]

IIRC for most packets, UDS are actually faster (not by a massive amount) than named pipes: https://stackoverflow.com/questions/1235958/ipc-performance-... and this advantage increases with packet size (from my own testing).

[parhamn]

TIL! Thanks for the link.

[renewiltord]

Have only seen the other way but shmem with a spinloop should be faster.