From owner-freebsd-xen@freebsd.org  Tue Feb  7 15:37:10 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 A59A1CD57F1
 for <freebsd-xen@mailman.ysv.freebsd.org>;
 Tue,  7 Feb 2017 15:37:10 +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 9551C36D
 for <freebsd-xen@FreeBSD.org>; Tue,  7 Feb 2017 15:37:10 +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 v17Fb9ca031554
 for <freebsd-xen@FreeBSD.org>; Tue, 7 Feb 2017 15:37:10 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: Tue, 07 Feb 2017 15:37:09 +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: <bug-212681-23905-mCIfUQBVBV@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: Tue, 07 Feb 2017 15:37:10 -0000

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

--- Comment #22 from Roger Pau Monn=C3=83=C2=A9 <royger@freebsd.org> ---
Hello,

I don't have much time to look into this right now, could you try to create=
 a
flamegraph [0] of this workload, this way we might be able to identify the
bottleneck(s). If possible you should create the flamegraph with pmcstat
instead of dtrace, the result is going to be much more accurate (specially =
when
running inside of a VM).

[0] http://www.brendangregg.com/blog/2015-03-10/freebsd-flame-graphs.html

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