From owner-freebsd-xen@freebsd.org Fri Feb 10 16:42:01 2017 Return-Path: Delivered-To: freebsd-xen@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 6D3E7CD92F6 for ; Fri, 10 Feb 2017 16:42:01 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4412C188 for ; Fri, 10 Feb 2017 16:42:01 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v1AGg0e2091733 for ; Fri, 10 Feb 2017 16:42:01 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-xen@FreeBSD.org Subject: [Bug 212681] I/O is slow for FreeBSD DOMu on XenServer Date: Fri, 10 Feb 2017 16:42:00 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.3-RELEASE X-Bugzilla-Keywords: performance X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: royger@freebsd.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-xen@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Feb 2017 16:42:01 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D212681 --- Comment #37 from Roger Pau Monn=C3=83=C2=A9 --- (In reply to Roger Pau Monn=C3=83=C2=A9 from comment #33) So I've run the dc3dd test on a FreeBSD VM, with 4 vCPUs and 4GB of RAM, against a block device on a spinning disk, nothing fancy, and this is what I get: (FreeBSD guest) # dc3dd wipe=3D/dev/ada1 dc3dd 7.2.641 started at 2017-02-10 16:19:54 +0000 compiled options: command line: dc3dd wipe=3D/dev/ada1 device size: 20971520 sectors (probed), 10,737,418,240 bytes sector size: 512 bytes (probed) 10737418240 bytes ( 10 G ) copied ( 100% ), 125 s, 82 M/s input results for pattern `00': 20971520 sectors in output results for device `/dev/ada1': 20971520 sectors out dc3dd completed at 2017-02-10 16:21:58 +0000 Then I shut down the guest, and ran the same test from Dom0 (Debian Linux 3= .16) against the same exact block device, and this is what I get: (Linux Dom0) # dc3dd wipe=3D/dev/dt51-vg/test dc3dd 7.2.641 started at 2017-02-10 16:31:34 +0000 compiled options: command line: dc3dd wipe=3D/dev/dt51-vg/test device size: 20971520 sectors (probed), 10,737,418,240 bytes sector size: 512 bytes (probed) 10737418240 bytes ( 10 G ) copied ( 100% ), 114 s, 90 M/s input results for pattern `00': 20971520 sectors in output results for device `/dev/dt51-vg/test': 20971520 sectors out dc3dd completed at 2017-02-10 16:33:28 +0000 So there's a < 10M/s difference, which I think it's fine (at the end there's always some overhead). I cannot really explain the results that you get, but I cannot also reprodu= ce your entire setup here. This is using the 12.0-CURRENT snapshot from 201702= 03. I'm afraid that unless we find a way for me to reproduce this, there's no w= ay that I can try to fix it. --=20 You are receiving this mail because: You are the assignee for the bug.=