Hrvoje Popovski [hrv...@srce.hr] wrote:
> if you're feeling brave enough and you can test/experiment
> with pf you can download openbsd kernel with experimental MP support
> from here http://kosjenka.srce.hr/~hrvoje/zaprocvat/smpfbsd
>
> SHA256 (smpfbsd) =
> e95e94190a0e52de7690b3278cfab1498581708
Not sure what do do know. Should I open a bug for more visibility?
To be honest, my WAN connection is way lower than the max
measured here with CURRENT, but I don´t want to discover when
upgrading to 6.5 that I lost 40% percent of performance again.
I would be more than happy to help with the inv
I am very brave indeed :)
OpenBSD 6.4 (GENERIC.MP) #0: Wed Oct 3 13:49:29 CEST 2018
hrv...@r620-2.srce.hr:/sys/arch/amd64/compile/GENERIC.MP
real mem = 1996279808 (1903MB)
avail mem = 1926565888 (1837MB)
mpath0 at root
scs
On 2018-10-04, Benjamin Petit wrote:
> I don't think the APU2 uses HT
correct
On 4.10.2018. 5:58, Benjamin Petit wrote:
> Ok so I compared 6.3-release, 6.3-release+syspatches(=stable?) and the latest
> snapshot from October 2.
>
> I measured iperf3 throughput between A and B, like this:
> PC A <---> APU2 <---> PC B
>
> pf rules are the one shipped by default in 6.3:
>
>
My sysctl output:
kern.ostype=OpenBSD
kern.osrelease=6.4
kern.osrevision=201811
kern.version=OpenBSD 6.4 (GENERIC.MP) #342: Tue Oct 2 23:23:09 MDT
2018
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.M
P
kern.maxvnodes=22282
kern.maxproc=1310
kern.maxfiles=7030
kern.argmax=
Added my sysctl output in attachement (I never really used
distribution lists before...)
I don't think the APU2 uses HT, but I tried with sysctl hw.smt=1,
no difference in the iperf3 numbers.
On Thu, 2018-10-04 at 05:02 +0100, Tom Smyth wrote:
> can you show us a copy of your sysctl output?
>
>
can you show us a copy of your sysctl output?
check if smt is disabled ... (Hyper Threading )
Im not sure if this would have an effect on the
APU2C2 ... but worth checking as it is a change
in behaviour between 6.3 and current AFIK
Thanks
Tom Smyth
On Thu, 4 Oct 2018 at 04:58, Benjamin Petit
Ok so I compared 6.3-release, 6.3-release+syspatches(=stable?) and the latest
snapshot from October 2.
I measured iperf3 throughput between A and B, like this:
PC A <---> APU2 <---> PC B
pf rules are the one shipped by default in 6.3:
gw# pfctl -sr
Hello, and thanks for your responses!
> My testing on OpenBSD 6.3 showed speeds of 750/s - 800Mb/s
> with default rules using x86-64 GENERIC (not i386)
Same setup as yours, and I definitely don't reach 750-800Mbits/s (550 at best)
When I transfer a big file from one network to another, I cle
On 2018-10-03, Benjamin Petit wrote:
> Before upgrading to CURRENT, I think routing with or without pf
> enabled was around 600Mbit/s, but I would need to reinstall to test
> again.
Snapshots are usually built with the "pool_debug" kernel option,
releases are built without it. This is good for fi
Hello,
your forwarding performance will vary based on a few things...
at the minute Routing is MP safe... but if one of the lan ports
lets say em1 was in a bridge... then the forwarding is done
by a single core...
My testing on OpenBSD 6.3 showed speeds of 750/s - 800Mb/s
with default rules us
Thanks, I just saw the previous discussion, from late 2017.
Do you know where we can follow the work that is being done? I would be more
than
happy to test early version.
it was discussed before in this mailing list. There is ongoing effort to make
pf more performant on multicore setup (what I understand).
There are more impacts like queue causes 100mbps drops in processing speed on
1Gbps link, etc...
Zbyszek
> Wiadomość napisana przez Benjamin Petit w dniu 03.
I am trying to setup a PC Engines APU2C2 as a router using OpenBSD. Using the
latest snapshots of CURRENT, with pf disabled, it seems capable to route at
near gigabit speeds, but when enabling pf (with the default config file), I
cannot get a bandwidth of more than 450/440Mbits/s between the two
15 matches
Mail list logo