Why is bandwidths of benchmark_tx.py and tunnel are different

I noticed that the bandwidths of benchmark_tx.py is wide and tunnel.py
is
narrow in the same frequency and same bit rate. I run uhd_fft on machine
A,
then run
./benchmark_tx.py -f 2.42G -r 1M
and
sudo ./tunnel.py -f 2.42G -r 1M
on machine B in turn. I got the uhd_fft wave as attached. Anyone can
explain why it happens? And is there any way to tune the bandwidth of
benchmark and tunnel?

On 06/26/2012 10:08 AM, Weixian Z. wrote:

I noticed that the bandwidths of benchmark_tx.py is wide and tunnel.py is
narrow in the same frequency and same bit rate. I run uhd_fft on machine A,
then run
./benchmark_tx.py -f 2.42G -r 1M
and
sudo ./tunnel.py -f 2.42G -r 1M
on machine B in turn. I got the uhd_fft wave as attached. Anyone can
explain why it happens? And is there any way to tune the bandwidth of
benchmark and tunnel?

Perhaps there is not data for tunnel.py to transmit? In contrast,
benchmark tx is constantly transmitting. -josh