From owner-freebsd-xen@freebsd.org  Mon Feb 13 15:58:56 2017
Return-Path: <owner-freebsd-xen@freebsd.org>
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 28A34CDDC52
 for <freebsd-xen@mailman.ysv.freebsd.org>;
 Mon, 13 Feb 2017 15:58:56 +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 186AAF1
 for <freebsd-xen@FreeBSD.org>; Mon, 13 Feb 2017 15:58:56 +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 v1DFwtaK051664
 for <freebsd-xen@FreeBSD.org>; Mon, 13 Feb 2017 15:58:55 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: Mon, 13 Feb 2017 15:58:55 +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: rainer@ultra-secure.de
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: <bug-212681-23905-q16XyEeiBR@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-212681-23905@https.bugs.freebsd.org/bugzilla/>
References: <bug-212681-23905@https.bugs.freebsd.org/bugzilla/>
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
 <freebsd-xen.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-xen>,
 <mailto:freebsd-xen-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-xen/>
List-Post: <mailto:freebsd-xen@freebsd.org>
List-Help: <mailto:freebsd-xen-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-xen>,
 <mailto:freebsd-xen-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Feb 2017 15:58:56 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D212681

--- Comment #57 from rainer@ultra-secure.de ---
Well, I did do dd test, but they only write on a filesystem.

It was (back then) most likely on ZFS, with compression etc. that changed t=
he
results.
Esp. if I just write zeros from /dev/null.

That's why I switched to dc3dd because it does the same thing on Linux and =
on
FreeBSD and completely eliminates the filesystem (and caching) layer as wel=
l as
any other kinds of write-optimization.


I've now created an empty UFS filesystem on my 50G volume and run unixbench=
 on
it.

--=20
You are receiving this mail because:
You are the assignee for the bug.=