CPU usage is quite time-consuming.(NativeUnixSocket.receive)

[wzfxue]

Describe the bug

I'm sorry, I'm not quite sure what caused the CPU usage to be particularly high.
Can you help me check if there is a problem with the code writing?

To Reproduce
Steps to reproduce the behavior:

1. com.sdtp.uds.JmsServer
2. com.sdtp.uds.JmsClient
   
   Expected behavior
   I am running JmsServer and JmsClient with 12 threads on a 48 core CPU host, which can generate approximately 4TB of data per minute, but the CPU usage is nearly 17%.
   
   Output/Screenshots
   If applicable, add console output/screenshots to help explain your problem.
   
   
   Notes
   Add any other context about the problem here. Please link/attach any source code that is useful to diagnose the issue.
   com.kohlschutter.junixsocket:junixsocket-native-common:2.10.1

JmsClient.java.txt
JmsServer.java.txt

[kohlschuetter]

I'm not sure I understand your concern, please clarify:

Your CPU is transferring 4 TB per Minute (68 GB per second), which you say it's 17% of your CPU, so 83% of your CPU is idle.

Doesn't sound too bad to me, especially when looking at what the code does.

Have you tried benchmarking it against some other implementation?

[wzfxue]

I'm not sure I understand your concern, please clarify:

Your CPU is transferring 4 TB per Minute (68 GB per second), which you say it's 17% of your CPU, so 83% of your CPU is idle.

Doesn't sound too bad to me, especially when looking at what the code does.

Have you tried benchmarking it against some other implementation?

---

Yes, I compared it with Java sockets, and for the same amount of data transmission, using TCP only takes up about 5% of the CPU. Perhaps it's because Unix domain sockets have low performance due to file system swapping, right?