Re: Periodic calls to sendto() vs bursts

davids wrote:

> Your 'sendto' is a blocking operation. It can take as long as it wants
> to. My bet is that the delay is caused by the receving rate of whatever
> you are sending data to.

(You snipped too much. There is no context left.)

You seem to have misunderstood the output of /usr/bin/time

0.12user 2.47system 1:40.01elapsed 2%CPU

means the process ran for 100 seconds, and 2.47 seconds (id est 7e9
cycles) were actively spent inside the kernel on behalf of the process.
Blocking in sendto() does not spin the CPU...

> What does the 'sendto' actually do? Is the TCP? UDP? Local? Remote?
> Or what?

It sends a UDP datagram to another PC on the same Ethernet LAN.


Spoon