From owner-freebsd-virtualization@freebsd.org Tue Mar 12 17:00:08 2019 Return-Path: Delivered-To: freebsd-virtualization@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 2807F1536ACD for ; Tue, 12 Mar 2019 17:00:08 +0000 (UTC) (envelope-from josh@tcbug.org) Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (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 0B2507137C for ; Tue, 12 Mar 2019 17:00:05 +0000 (UTC) (envelope-from josh@tcbug.org) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 05F2C22903 for ; Tue, 12 Mar 2019 13:00:04 -0400 (EDT) Received: from imap2 ([10.202.2.52]) by compute1.internal (MEProxy); Tue, 12 Mar 2019 13:00:04 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:message-id:subject :to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm2; bh=nPw6uComkkuEhrjgq0B5xfVp2P1z5dUFZ5wAc4exk5o=; b=cwKJyGw5 mjTNo7fvZqx80uZumHz3XXb1jnf635ZDpXmtOCua1uRd3uDELQIIadwAn+AHWaXv Z9MOVpFxXubAIU1XJGS8aVXk3SFRcEfyVcjJRz7+CpvCK0XpQyMEXotq7Z/5N4Pt A6iDtlBm8gDlfjGBunFqea37hy+WxUrIpB8XPQSS4GQpIskdJYMHzN8NEuBXLg8J 6GDZrkz6/gZKrP/xSiznpgYAH3tuEnkGPcuxUxduKKLJH06+wrKWfMNJi5GTjohi WWo3jcc0wKWZGGB8Xo/HsYdBdOSknA37ABQV+zH9GFWWULB5ZbBv8TAruLus86bn jbm7IwBrG8zCsg== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedutddrgeekgdeljecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepofgfkfffhffvufgtsehttdertderre dtnecuhfhrohhmpedflfhoshhhucfrrggvthiivghlfdcuoehjohhshhesthgtsghughdr ohhrgheqnecurfgrrhgrmhepmhgrihhlfhhrohhmpehjohhshhesthgtsghughdrohhrgh enucevlhhushhtvghrufhiiigvpedt X-ME-Proxy: Received: by mailuser.nyi.internal (Postfix, from userid 501) id 014F37C538; Tue, 12 Mar 2019 13:00:02 -0400 (EDT) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.1.5-925-g644bf8c-fmstable-20190228v5 X-Me-Personality: 4359293 Message-Id: <0219ca84-a0b7-438d-b43c-28526d505d98@www.fastmail.com> Date: Tue, 12 Mar 2019 13:01:17 -0400 From: "Josh Paetzel" To: freebsd-virtualization@freebsd.org Subject: Azure disk performance issue Content-Type: text/plain X-Rspamd-Queue-Id: 0B2507137C X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org; dkim=pass header.d=messagingengine.com header.s=fm2 header.b=cwKJyGw5 X-Spamd-Result: default: False [-6.23 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-0.998,0]; R_DKIM_ALLOW(-0.20)[messagingengine.com:s=fm2]; XM_UA_NO_VERSION(0.01)[]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; IP_SCORE(-3.40)[ip: (-8.88), ipnet: 66.111.4.0/24(-4.60), asn: 11403(-3.46), country: US(-0.07)]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-virtualization@freebsd.org]; TO_DN_NONE(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; RCVD_COUNT_THREE(0.00)[4]; DMARC_NA(0.00)[tcbug.org]; DKIM_TRACE(0.00)[messagingengine.com:+]; MX_GOOD(-0.01)[in2.smtp.messagingengine.com,in1.smtp.messagingengine.com,in2.smtp.messagingengine.com,in1.smtp.messagingengine.com,in2.smtp.messagingengine.com,in1.smtp.messagingengine.com]; NEURAL_HAM_SHORT(-0.93)[-0.932,0]; R_SPF_NA(0.00)[]; RCVD_IN_DNSWL_LOW(-0.10)[26.4.111.66.list.dnswl.org : 127.0.5.1]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:11403, ipnet:66.111.4.0/24, country:US]; RCVD_TLS_LAST(0.00)[]; MID_RHS_WWW(0.50)[] X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Mar 2019 17:00:08 -0000 I have an issue where a FreeBSD VHD in Azure performs well when reading, and it performs well when writing, but if you throw a mixed read/write workload at it the write performance drops to near zero and latency starts spiking to several hundred milliseconds. Interestingly enough read performance improves under these conditions. Looking for some troubleshooting help. -- Thanks, Josh Paetzel