From owner-freebsd-geom@freebsd.org Mon Oct 24 19:20:30 2016 Return-Path: Delivered-To: freebsd-geom@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D1EA7C1F8BF for ; Mon, 24 Oct 2016 19:20:30 +0000 (UTC) (envelope-from 1983-01-06@gmx.net) Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2F37D764 for ; Mon, 24 Oct 2016 19:20:29 +0000 (UTC) (envelope-from 1983-01-06@gmx.net) Received: from [192.168.1.6] ([79.247.119.52]) by mail.gmx.com (mrgmx001) with ESMTPSA (Nemesis) id 0MKYLf-1bxNDO2M7D-0022Hp for ; Mon, 24 Oct 2016 21:20:21 +0200 Subject: Re: Abysmally slow write to geom class volume over network To: freebsd-geom@freebsd.org References: <33da0f73-48f1-4727-fe76-41343dc4955b@gmx.net> From: Michael Osipov <1983-01-06@gmx.net> Message-ID: Date: Mon, 24 Oct 2016 21:20:20 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: <33da0f73-48f1-4727-fe76-41343dc4955b@gmx.net> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:DfFIBED7VqY8DarvGmkMClnVTonrB/ksZ/TIeso5Vipfw5+nMdd HcrwprvozwdwJFW62ulRTi9AAHNWYuoTJxY4gUML0zIL8NyV0ffteklP/w5SHHNLLaDixqK Xeze2doZD2bLWklNPAfvIFmGCE2UEeGh1zHRC3GMDWg+Zdl3U9W6/DAHAcgABnhlBafGv6d /nYIlKx0AocUsHAr65Rmg== X-UI-Out-Filterresults: notjunk:1;V01:K0:qbljixUu+tA=:zmi/WpyCB+l6hkH/fTTW82 fXVIPtJXV8R8iAmeFwxVLIxnOGYbFDeBzY/8RVAoUaeHiI6kPkfoGvMnl+7B33C3QJNfJ2Vui l51c3kCAkoLy/fcilZRjNqEIWpqHYyihuiu1uWfOA1+bqbnFGdBjBKTnBXnJsD0fZZE9rgJgP myu+aTJcGHhDBI9xGyb/+4XjBxEiaP8zeqcf2zKsJ3p6rgWWqgXtULhfm3n/n7VtvFxC9DJDE 6Uypg3QisbJpv2p9H7q4bXQJdr/Hn9SN+azmPs0LO8mFd06cX3hSLzHtnJ5n07iwohLX0sDgo DLWXfqarRrejd//s/aA19K2C8gy+IJerI7weQXzFaIJS+tIR+i3yWxDMx1j5fIVB/nb4ZU9kn hyT3GHRYnHJySJY9QiwH6ro5HfwoP/mKgdeyAfLnmCHkFRukDXb8dTuYN9sKtX2O9oWi/d3kd mPK9tjKGz8IHN2b/0tzZe/zJ1z2KfX9Fwf7RMcjS+X9yHkaTj8/Wg8pvRM8x5L41+NXrNHVMh oD5yt7CqF7iXzxnb9YUMSm4FZ+Zqm0Bf5PrUXSlwms9UWxrg3194CSRsa7RDo/Me+DKWs8HuM 7rjGhhrWzUvXNG8Pf41enmbhAv8/mVWlLlKYEF5lTeQMdhlZFnZlHZRSn0eu8R8p4Oz5Hqlqu BwKw2HhwJfrnjTCdlFulo6+mdBf7yFN0Nd3H0uAGNE9fP7Dq22Wjhub4qHbqkdMg3gplFYVmY k1EQazXwAn0o6yyL+MoOwpgBApc7MBsMNbsdDtz0119npXF+SMoP2BfzT2rcjFBNjTPy52/2Q P779r+p X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Oct 2016 19:20:30 -0000 Am 2016-10-06 um 20:34 schrieb Michael Osipov: > Hi folks, > > I am experiecing a performance breakdown when writing to some geom class > volume over network. I have tried SCP/SFTP, SMB, nc, ggated/ggatec from > Windows 10 and FreeBSD 10.3-RELEASE and I receive at most 500 kB/s. > Reading is superfast as well as writing to a regular, non-geom volume, > network is fully saturated. > > I am on: > # uname -a > FreeBSD bsd1home 10.3-RELEASE-p7 FreeBSD 10.3-RELEASE-p7 #0: Thu Aug 11 > 18:37:29 UTC 2016 > root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC i386 > > Any idea what the problem is? How can I investigate on the penality in > performance? FWIW, this problem is unlikely rooted in geom at all. I have added a second NIC into the machine, Reatek 8139 rl0 (yes -- I know it's crap), and performed the same setup: maximum speed. Conclusion for me is rather my NIC is broken or the driver. I suspect the driver to be. The link state was going down and up over and over again. The same issue has been reported here [1], [2] a couple of years ago. I will repost this to freebsd-net or rather to bugs.freebsd.org Michael [1] http://forums.nas4free.org/viewtopic.php?t=3606 [2] http://www.mail-archive.com/freebsd-net@freebsd.org/msg11038.html From owner-freebsd-geom@freebsd.org Wed Oct 26 15:54:54 2016 Return-Path: Delivered-To: freebsd-geom@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BF5D8C2089A for ; Wed, 26 Oct 2016 15:54:54 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from onlyone.friendlyhosting.spb.ru (onlyone.friendlyhosting.spb.ru [IPv6:2a01:4f8:201:6350::2]) by mx1.freebsd.org (Postfix) with ESMTP id 8D652BCC for ; Wed, 26 Oct 2016 15:54:54 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from [192.168.17.133] (unknown [89.113.128.32]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.friendlyhosting.spb.ru (Postfix) with ESMTPSA id 645C866B for ; Wed, 26 Oct 2016 18:54:52 +0300 (MSK) Reply-To: lev@FreeBSD.org To: freebsd-geom@freebsd.org From: Lev Serebryakov Subject: Does "gpart delete" send TRIM (BIO_DELETE) for freed space? Organization: FreeBSD Message-ID: <74609c38-4bdb-44bc-aedc-1bd5957bbbee@FreeBSD.org> Date: Wed, 26 Oct 2016 18:54:50 +0300 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Oct 2016 15:54:54 -0000 I want to cleanup and TRIM partition on my SSD (it was used for L2ARC, not for any FS). Is it enough to call "gpart delete" or I need to send "TRIM" request(s) manually? If I need to send TRIM manually, how can I do this? -- // Lev Serebryakov