> > this is very illuminating. it says that initially, tcp send/receive
quoted text > > window is your bottleneck. when you increase them to 131072, the cpu
> > becomes your bottleneck and remains that way no matter what else you
> > tweak (idle drops to 0.0% and stays there).
> >
> > the next question is, of course, why is your cpu spending all its time
> > in "system" and "interrupt"? is it doing unnecessary work, or is the
> > work necessary and your cpu just isn't fast enough? I don't have ready
> > answers to these questions.
> >
> > -ken
> >
>
> Hello,
>
> I see, that while I am testing network speed by iperf, 100% CPU is being
> used, but is that normal for default install of OpenBSD 4.8 with default
> pf.conf??
>
> I have second computer exactly like that one (IBM ThinkCentre A51P), on
> which i am running this tests but with P4 3Ghz CPU 2mb cache (not
> celeron 2.8) and the same is happening (100% CPU).
>
> LAN interface is Intel PRO/1000 PT Desktop Adapter (PCIe, model:
> EXPI9300PTBLK) and this is the only pcie adapter in computer (maybe
> broadcom integrated nic is also pcie but is not used)
>
> So the conclusion might be:
> - there is problem with my Intel NIC model/cheapset
> - there is problem with em driver
> - there is problem with my hardware (I need serwer motherboard with pcie
> and pci 64bit 66mhz)
> - I need faster CPU than P4 3GHz ??
or
- there is a problem with iperf :)
How about measuring with something else? Did you try tcpbench? Or something
even simpler, like scp-ing from /dev/null to /dev/null? With pf and queues
enabled you can monitor the B/S rate.
