When sending messages to 127.0.0.1 (or the localhost) the internal network driver typically handles this by shortcutting a few steps. If you have a networksniffer/protocol analyzer like wireshark, it can not see these shortcutted packets. By using a loopback adapter, the messages get send much further through the stack, enabling programs like wireshark to capture … Read more
In latest version, you can run your script with: ./jmeter-server -Djava.rmi.server.hostname=xxx.xxx.xxx.xxx Replace xxx.xxx.xxx.xxx with this server’s IP address, i.e., the IP address that the controlling jmeter machine will use to connect to this server.
You might do it like this, without much hassle: # kpartx -v -a logging-test.img add map loop0p1 (251:0): 0 497664 linear /dev/loop0 2048 add map loop0p2 (251:1): 0 66605058 linear /dev/loop0 501758 add map loop0p5 (251:2): 0 66605056 251:1 2 # ls /dev/mapper/ control loop0p1 loop0p2 loop0p5 # mount /dev/mapper/loop0p1 /mnt/test # mount | grep … Read more
Your best source of information is the issue you linked to docker#5618. This is a kernel bug, and has not yet been resolved. The issue is “triggered” by docker because starting/stopping containers also creates network interfaces for containers when they are created/destroyed.
Yes, local interprocess communication by unix domain sockets should be faster than communication by loopback localhost connections because you have less TCP overhead, see here.