CURRENT as gateway on not-so-fast hardware: where is a bottlneck?

[Ian FREISLICH]

Lev Serebryakov wrote:
> Hello, Lev.
> You wrote 15 =D0=B0=D0=B2=D0=B3=D1=83=D1=81=D1=82=D0=B0 2012 =D0=B3., 0:45:=
> 42:
> 
> LS>  Answer looks trivial: router CPU is bottleneck. But here is one additi=
> onal
> LS> detail: `top' never shows less than 50% of idle when torrents are
> LS> active. And `idle' time with torrents traffic is ALWAYS is higher than
> LS> without them, but with WiFi traffic.
>   Ok,  additional  information:  it  seems,  that  `top'  is liar when
>  POLLING is enabled for em0 and vr1 NICs. I'm turned POLLING off, and
>  speeds are the same, but `idle' is no more 50%, it is `0%' when
>  gateway is overloaded.
> 
>  But i still feezes under load with ULE. It looks like ULE is broken.

Are you sure it's a freeze and not a panic?  I'm seeing very frequent
panics on -CURRENT running as a gateway.  Often, it doesn't come
back without a powercycle because it's unable to complete a crashdump.

Ian

-- 
Ian Freislich