Date: Wed, 12 Oct 2016 18:41:43 -0700 From: John-Mark Gurney <jmg@funkthat.com> To: Michael Osipov <1983-01-06@gmx.net> Cc: freebsd-geom@freebsd.org Subject: Re: Abysmally slow write to geom class volume over network Message-ID: <20161013014143.GA1669@funkthat.com> In-Reply-To: <15e9cb94-7ad8-e547-b06a-699ce2250624@gmx.net> References: <33da0f73-48f1-4727-fe76-41343dc4955b@gmx.net> <18314f27-849b-31df-d88d-af64e89c133f@gmx.net> <346c7da7-02b2-ba34-1463-f3f0a5a3cd9a@rlwinm.de> <15e9cb94-7ad8-e547-b06a-699ce2250624@gmx.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Michael Osipov wrote this message on Wed, Oct 12, 2016 at 20:54 +0200:
> As if there is a bottleneck between socket read and geom write to FS.
>
> Is that better?
Have you run gstat on the system to see if there is an IO bottle
neck? Since you are using graid3, you want to look to see if
it's %busy is ~100, while the underlying components are not.
Also, if you do dd if=/dev/zero of=/mnt/somefile bs=1m count=1024,
from the local system, are things still slow?
P.S. This is basic debugging, have to identify which part of the
system is misbehaving.
P.P.S. Your "non-geom" test is still using geom, just not w/ the graid3
module.
--
John-Mark Gurney Voice: +1 415 225 5579
"All that I will do, has been done, All that I have, has not."
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20161013014143.GA1669>