--- On Tue, 9/7/10, bsd <[email protected]> wrote: > From: bsd <[email protected]> > Subject: Re: [pfSense Support] Benchmark tool > To: [email protected] > Date: Tuesday, September 7, 2010, 3:24 PM > Here are the results of the test you > have asked : > > gregober 21:15:31 ~ -> iperf -c 1.2.3.5 > ------------------------------------------------------------ > Client connecting to 1.2.3.5, TCP port 5001 > TCP window size: 129 KByte (default) > ------------------------------------------------------------ > [ 3] local 192.168.10.2 port 60681 connected with > 1.2.3.5 port 5001 > [ ID] Interval > Transfer > Bandwidth > [ 3] 0.0-10.0 sec 1.07 > GBytes 919 Mbits/sec > > Ubuntu 10.04 LTS freshly baked. > > > I think this has to be compared to this test : > > > WITHOUT PACKET FILTERING ENABLED > > gregober 18:40:12 ~ -> iperf -c 1.2.3.4 > > > ------------------------------------------------------------ > > Client connecting to 1.2.3.4, TCP port 5001 > > TCP window size: 129 KByte (default) > > > ------------------------------------------------------------ > > [ 3] local 192.168.1.199 port 53391 connected > with 1.2.3.4 port 5001 > > [ ID] Interval > Transfer > Bandwidth > > [ 3] 0.0-10.0 sec 1.03 > GBytes 882 Mbits/sec > > Results are somewhat similar… > > My main question is why when filtering is enabled do we > loose 75% of the throughput… > > Is this normal figures or not ? > > > Thank you. > You should definitely see CPU load, you mentioned that you did not see anything close to CPU saturation. Could you please post top -S with filtering enabled and disabled. Thanks.
Evgeny. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] Commercial support available - https://portal.pfsense.org
