Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

How much of the CPU bandwidth is consumed copying payload data across the socket API interface in send() or recv() system calls?

0
10 Posted

How much of the CPU bandwidth is consumed copying payload data across the socket API interface in send() or recv() system calls?

0
10

A. On a 1-GHZ Intel Pentium III CPU with PC133 memory, about 46 percent of the CPU is consumed copying data in send() and recv() socket API system calls during a TCP/IP transfer at 110 megabytes per second (MB/sec) and about 24 percent on a 2-GHZ Intel Xeon CPU with DDR SDRAM. Based on this and the benchmark CPU utilizations, this would indicate that these Socket API buffer copies are likely the most significant single CPU/memory overhead factor in TCP/IP over Gigabit Ethernet — much more so than the TCP/IP protocol stack itself.

Related Questions

What is your question?

*Sadly, we had to bring back ads too. Hopefully more targeted.

Experts123