What to listen PHP-FPM: socket vs port?

Question

linux

Run PHP-FPM on socket or port? Pros, cons, pitfalls?

Most of all, the question of speed is of interest, and, in particular, the overhead of communicating with the demon. Maybe someone did a benchmark?

If there is something specific to freebsd, it's also interesting.

Answer 1

Sockets work a little bit faster, but in reality, they quickly fall off, because. the allowed number of open handles has been exceeded.
We use the port, the speed is practically the same.

Answer 2

From my own experience, I can only say that it works faster and more stable through sockets. Just freebsd (6-8).

Answer 3

This is an inter-process communication issue, but sockets are considered to be faster than the network protocol.

Answer 4

But in my experience I say with confidence that it works better on ports.
Sysctl did not help in any way. I kept it on sockets for a week and switched to ports. After that, the number of dumps dropped to almost zero.
Do the tests yourself. The same ab utility will help with this.

Answer 5

Well, if everything is childish on one server, then the socket, if the fronts are on the other, then the port.

Answer 6

If the connection is local, then a Unix socket is generally preferred. It can work up to 30% faster. You can manage access rights at the FS level.
In general, I will support opium in the thesis if the backend is local, then the Unix socket.