From owner-freebsd-bugs@freebsd.org Fri Jun 21 07:17:47 2019 Return-Path: Delivered-To: freebsd-bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0B61715D2B12 for ; Fri, 21 Jun 2019 07:17:47 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 6137083760 for ; Fri, 21 Jun 2019 07:17:46 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 2219815D2B0F; Fri, 21 Jun 2019 07:17:46 +0000 (UTC) Delivered-To: bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DAD3215D2B0E for ; Fri, 21 Jun 2019 07:17:45 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 79CE18375A for ; Fri, 21 Jun 2019 07:17:45 +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 mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id A027716479 for ; Fri, 21 Jun 2019 07:17:44 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id x5L7HiDG061992 for ; Fri, 21 Jun 2019 07:17:44 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x5L7HioG061982 for bugs@FreeBSD.org; Fri, 21 Jun 2019 07:17:44 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 238733] kvm disk i/o extremely slow Date: Fri, 21 Jun 2019 07:17:44 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 12.0-RELEASE X-Bugzilla-Keywords: 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: bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter Message-ID: 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-bugs@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Jun 2019 07:17:47 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D238733 Bug ID: 238733 Summary: kvm disk i/o extremely slow Product: Base System Version: 12.0-RELEASE Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: rainer@ultra-secure.de Hi, I've posted this on the forum: https://forums.freebsd.org/threads/is-kvm-virtio-really-that-slow-on-freebs= d.71186/#post-430366 But I'll reiterate here. Basically, I'm running a FreeBSD 12 image created alongside this document: https://docs.openstack.org/image-guide/freebsd-image.html (plus swap) On a KVM host that is, TTBOMK, Ubuntu 18. Storage is Ceph Blockstorage, usi= ng pure NVMe SSDs - but I/O is capped at 2000 IOP/s. Using CentOS as a KVM guest, I basically get this: [root@centos ~]# dc3dd wipe=3D/dev/sdb dc3dd 7.1.614 started at 2019-06-20 07:54:22 +0000 compiled options: command line: dc3dd wipe=3D/dev/sdb device size: 83886080 sectors (probed) sector size: 512 bytes (probed) 42949672960 bytes (40 G) copied (100%), 342.37 s, 120 M/s=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20 input results for pattern `00': 83886080 sectors in output results for device `/dev/sdb': 83886080 sectors out dc3dd completed at 2019-06-20 08:00:05 +0000 Using FreeBSD, I get this: root@freebsd:~ # dc3dd wipe=3D/dev/vtbd2 dc3dd 7.2.646 started at 2019-06-20 09:37:10 +0200 compiled options: command line: dc3dd wipe=3D/dev/vtbd2 device size: 83886080 sectors (probed), 42,949,672,960 bytes sector size: 512 bytes (probed) 42949672960 bytes ( 40 G ) copied ( 100% ), 4585 s, 8.9 M/s=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20 input results for pattern `00': 83886080 sectors in output results for device `/dev/vtbd2': 83886080 sectors out dc3dd completed at 2019-06-20 10:53:35 +0200 The forum posting has fio-runs with the actual I/O numbers. Are the drivers really that bad? If this is the situation, FreeBSD is completely useless in the cloud. At le= ast for us. --=20 You are receiving this mail because: You are the assignee for the bug.=