On Jul 08 22:07:53, pha...@gmx.de wrote:
> Hi David, hi Jan. Thanks for your response.
>
> On Mon, 8 Jul 2013 09:00:52 +0200
> Jan Stary <h...@stare.cz> wrote:
>
> > How is the filesystem mounted on the OpenBSD NFS server,
> > how is it exported, and how is it mounted on the Win client?
>
> the output of mount:
>
> /dev/wd0a on / type ffs (local)
> /dev/wd0e on /home type ffs (NFS exported, local, nodev, nosuid)
> /dev/wd0d on /usr type ffs (local, nodev)
> /dev/sd0a on /usr/src type ffs (NFS exported, local, nodev, softdep)
> localhost:/home/phancy/www on /var/www/htdocs type nfs (nodev, nosuid,
> v3, udp, soft, intr, timeo=100)
>
> my exports file:
>
> # $OpenBSD: exports,v 1.2 2002/05/31 08:15:44 pjanzen Exp $
> #
> # NFS exports Database
> # See exports(5) for more information. Be very careful: misconfiguration
> # of this file can result in your filesystems being readable by the world.
>
> /home/phancy/www -ro localhost
> /usr/src/media -network 192.168.2 -mask=255.255.255.0
>
> mounted on win simply with Ultimate Build-in NFS Client,
> here the command:
>
> mount \\192.168.2.108\usr\src\media H:
Details matter. Is this NFS2/NFS3? Is this a tcp/udp mount?
mount_nfs (as we know it on BSD) offers quite a few options
that can make a difference. Does the Win client have any
options?
In particular, being a video server, I suppose the Win client
does long sequential reads. I remember -r speeding it up.
> openbsd nfs server as iperf client to windows
> $ iperf -c 192.168.2.106
> ------------------------------------------------------------
> Client connecting to 192.168.2.106, TCP port 5001
> TCP window size: 17.0 KByte (default)
> ------------------------------------------------------------
> [ 3] local 192.168.2.108 port 11633 connected with 192.168.2.106 port
> 5001 [ ID] Interval Transfer Bandwidth
> [ 3] 0.0-10.0 sec 566 MBytes 475 Mbits/sec
>
> openbsd nfs server as iperf server, windows as client:
> $ iperf -s
> ------------------------------------------------------------
> Server listening on TCP port 5001
Is your NFS mount a TCP mount?
> TCP window size: 16.0 KByte (default)
> ------------------------------------------------------------
> [ 4] local 192.168.2.108 port 5001 connected with 192.168.2.106 port
> 49449 [ ID] Interval Transfer Bandwidth
> [ 4] 0.0-10.0 sec 516 MBytes 432 Mbits/sec
>
> If I boot both devices to openbsd, iperf shows:
>
> $ iperf -c 192.168.2.106
> ------------------------------------------------------------
> Client connecting to 192.168.2.106, TCP port 5001
> TCP window size: 31.1 KByte (default)
> ------------------------------------------------------------
> [ 3] local 192.168.2.108 port 22735 connected with 192.168.2.106 port
> 5001 [ ID] Interval Transfer Bandwidth
> [ 3] 0.0-10.0 sec 559 MBytes 469 Mbits/sec
> $ iperf -s
> ------------------------------------------------------------
> Server listening on TCP port 5001
> TCP window size: 16.0 KByte (default)
> ------------------------------------------------------------
> [ 4] local 192.168.2.108 port 5001 connected with 192.168.2.106 port
> 28918 [ ID] Interval Transfer Bandwidth
> [ 4] 0.0-10.0 sec 807 MBytes 675 Mbits/sec
> So the "OpenBSD network" seems to be faster, but with 469Mbit/sec too
> slow as an HD Videoserver.
The 469 is what iperf does, not how fast your NFS client can read.
> Perhaps the PCI bus, perhaps the PCI NIC itself, or some bridge?
> I'm not well versed in it, but it is the old
> hardware for sure. Is it worth digging?
It would be my wild guess that the NFS is your bottleneck
(rather than the hardware). Try various (NFS) mount options.
Jan
BTW,
(1) why are you poluting a standardized directory like /usr/src
with something like /usr/src/media, serving videos?
(2) why are you "exporting" /home/phancy/www to /var/www/htdocs,
on your 2G wd0 disk?
