From owner-freebsd-virtualization@freebsd.org Wed Mar 13 00:41:36 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 AC78A15452B1 for ; Wed, 13 Mar 2019 00:41:36 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from wout2-smtp.messagingengine.com (wout2-smtp.messagingengine.com [64.147.123.25]) (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 9B5738E30E for ; Wed, 13 Mar 2019 00:41:35 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.west.internal (Postfix) with ESMTP id E9830393D for ; Tue, 12 Mar 2019 20:41:33 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Tue, 12 Mar 2019 20:41:34 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zyxst.net; h= date:from:to:subject:message-id:references:mime-version :content-type:in-reply-to; s=fm2; bh=gX9McWph1Y6ZZOL/OrscKfND2Je 1WkGqVvew4/sEaDo=; b=gfAdvdH2O6Wo6mjMMKEm3GfcBj/wWFRUhyPLamMw4Rl rJxwrEIdF5iz9fSyEvuArh3VapogLvT4wBbm3ojcMEqaobc7dV6c6gGNcnDhGWyL tg2IiZBKYMhhulaGbul0+TO84sV60A0C7JrfsJ7JoVeed0bKx++iJmu419O9DkWt +b9xMSeqQgKg95tmTb9vNM33XlXpKJfvh6+3CYIqEjkFoHYsa/RFo2zFtMs6DJ8M kC9mHb4YFX6MFftJo9GFxKaaFgRQ14BBHKXayDyl7VZrDylM9BZeaN5SreW2n0l3 uBmFwpEyBCoGxpjJYVMazDiTzI9+jnxRGzAkrSk8t3A== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=gX9McW ph1Y6ZZOL/OrscKfND2Je1WkGqVvew4/sEaDo=; b=1fsyp5zvpgn1FBGXNN7Ej1 Q7W7dTbwQxof9KMneN7VFjkkey+m5C3X5MyfgxfNPeId2Cqccte+NSacki4d9zqe ifcjful6wC4whLkR4fmnD8W28+8Y/2pASRe1obdnXiOm4xHk8vGi2gHziOHqBscc BrpAVg67hyVAa9MXaVpmyEJwGmJ2j/OKrBFBjFq/KtZfPNj+7xRMnz2s24tzhijd Ze1Asg5IEufYIU7jyEEduSF7nChYOUN25mpaDJE2w4Hjqn02eJhZA8p0TUVq57Sm VKW4giH0Rb4MHSirYYc/xg7dvfG1ZxGJt5A/Wa4kRn4aZCnMYWcvcMlJsGJfhM2w == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedutddrgeelgddvfecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepfffhvffukfhfgggtuggjfgesthdtre dttdervdenucfhrhhomhepthgvtghhqdhlihhsthhsuceothgvtghhqdhlihhsthhsseii hiigshhtrdhnvghtqeenucfkphepkedvrdejtddrledurddutddunecurfgrrhgrmhepmh grihhlfhhrohhmpehtvggthhdqlhhishhtshesiiihgihsthdrnhgvthenucevlhhushht vghrufhiiigvpedt X-ME-Proxy: Received: from rpi3.zyxst.net (rpi3.zyxst.net [82.70.91.101]) by mail.messagingengine.com (Postfix) with ESMTPA id D96F110336 for ; Tue, 12 Mar 2019 20:41:32 -0400 (EDT) Date: Wed, 13 Mar 2019 00:41:30 +0000 From: tech-lists To: freebsd-virtualization@freebsd.org Subject: Re: Azure disk performance issue Message-ID: <20190313004128.GA33467@rpi3.zyxst.net> Mail-Followup-To: freebsd-virtualization@freebsd.org References: <0219ca84-a0b7-438d-b43c-28526d505d98@www.fastmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: <0219ca84-a0b7-438d-b43c-28526d505d98@www.fastmail.com> User-Agent: Mutt/1.11.2 (2019-01-07) X-Rspamd-Queue-Id: 9B5738E30E X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org; dkim=pass header.d=zyxst.net header.s=fm2 header.b=gfAdvdH2; dkim=pass header.d=messagingengine.com header.s=fm2 header.b=1fsyp5zv; spf=pass (mx1.freebsd.org: domain of tech-lists@zyxst.net designates 64.147.123.25 as permitted sender) smtp.mailfrom=tech-lists@zyxst.net X-Spamd-Result: default: False [-6.97 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_DKIM_ALLOW(-0.20)[zyxst.net:s=fm2,messagingengine.com:s=fm2]; NEURAL_HAM_MEDIUM(-1.00)[-0.999,0]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:64.147.123.25]; TO_MATCH_ENVRCPT_ALL(0.00)[]; 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)[zyxst.net]; MX_GOOD(-0.01)[cached: in2-smtp.messagingengine.com]; DKIM_TRACE(0.00)[zyxst.net:+,messagingengine.com:+]; NEURAL_HAM_SHORT(-0.98)[-0.985,0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:11403, ipnet:64.147.123.0/24, country:US]; IP_SCORE(-3.37)[ip: (-8.89), ipnet: 64.147.123.0/24(-4.44), asn: 11403(-3.46), country: US(-0.07)]; RCVD_IN_DNSWL_LOW(-0.10)[25.123.147.64.list.dnswl.org : 127.0.5.1] 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: Wed, 13 Mar 2019 00:41:36 -0000 On Tue, Mar 12, 2019 at 01:01:17PM -0400, Josh Paetzel wrote: > 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. I'm very new to freebsd on azure so unfortunately can't be much help at least initially, but I'd be interested to know what sort of loads you're putting on it, and what resources the VM has (I mean # of cpu, ram, size). Any particular software triggering the problem? I have had to manage php5/mysql on a system where the "disk" was NFS or something very similar and sometimes it'd thrash under not a particularly heavy load. But that was years ago on linux. Some software needs attention or a setting for something like flock or dotlock or similar when used in a non-baremetal situation. -- J.