Re: [lwip-users] LWIP UDP throughput with Iperf

2016-09-16 Thread Sergio R. Caprile
Data size can't be 2MB/s, by data size I mean the size of the data chunks you are handling in each frame, you expect to handle an amount of data in a period of time, and that data is handled in pieces, if pieces are too short you need to handle many pieces, if pieces are too long, you need more

Re: [lwip-users] LWIP UDP throughput with Iperf

2016-09-16 Thread Arpit Agarwal
.   Thanks, Arpit         - Original Message - Sender : Sergio R. Caprile  Date : 2016-09-16 18:09 (GMT+5:30) Title : Re: [lwip-users] LWIP UDP throughput with Iperf  The amount of memory used depends on your application. There is no reason to queue UDP datagrams unless you

Re: [lwip-users] LWIP UDP throughput with Iperf

2016-09-16 Thread Sergio R. Caprile
The amount of memory used depends on your application. There is no reason to queue UDP datagrams unless you don't get them as they come. API ? NO_SYS ? port ? layer-2 driver ? data size ? stats ? frames per second ? memory usage ? app details ? If you are expecting high-performance, you should be

[lwip-users] LWIP UDP throughput with Iperf

2016-09-14 Thread Arpit Agarwal
Hi, I am trying to measure LWIP UDP performance on loopback interface using iperf. I am getting very low throughput (around 5 Mbps). If I try to set more bandwidth in iperf , LWIP run put of memory and I have to allocate more memory (MEM_SIZE) to resolve memory failure. To achieve successfu