Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gwdDl-0008Ja-9F for pgsql-performance@arkaria.postgresql.org; Thu, 21 Feb 2019 01:32:17 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1gwdDj-0003Hd-Ji for pgsql-performance@arkaria.postgresql.org; Thu, 21 Feb 2019 01:32:15 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gwdDj-0003HW-5H for pgsql-performance@lists.postgresql.org; Thu, 21 Feb 2019 01:32:15 +0000 Received: from mail-io1-xd34.google.com ([2607:f8b0:4864:20::d34]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gwdDf-0006CE-Pp for pgsql-performance@lists.postgresql.org; Thu, 21 Feb 2019 01:32:13 +0000 Received: by mail-io1-xd34.google.com with SMTP id p17so129412iol.7 for ; Wed, 20 Feb 2019 17:32:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telsasoft-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=JDTOChmF3qmNA4hfV18Gx1SEmXsjUfcAxwkkf27Pwro=; b=dA71muJ2JATmv1lkGb8y3KzlMaNmkquIC3rOnRHNiNTSF09J5I/ga5npMVeFDlxbC7 dlQEXIqccId342UlFKmbLhkpc2uYdQaQVlTx7bmXnrnlF2oJYk63ulEISlSGqh7+n18V M3KK1nKaH6+Iyh65vEAMklq/h8W1wICOPNzQkxDHOq+1qrw7AbbJDICRHbZL/B/nSKH5 pmuUos3eyuxTdRbRyShsQQGlnnrld6g/YimlrY99BMnglbpn9w4OlePib79WLBODA86N RF6x2Wcre8lFa1xLQsjmA+Q3Lz2K4xa9KLG6iMwXUSNAFizNxdB86lNS23wPK3OShSTG QNKA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=JDTOChmF3qmNA4hfV18Gx1SEmXsjUfcAxwkkf27Pwro=; b=StgBnVU/SUr9yQBnZrMrhxq/GiM3kcINDep+WDIridDEQwpChGT8eE9q0/M75mO9Yj Pr63o9kIbCdTapSvShjoxuTj+ctKJ4nYso7VAlLh+yrTmPEPcpp0oCMn1mlXoHCLRPgE WQLT7KpZDafA59Gbdhze2A5an5laWEPudklixxfgRVoWXaswv3Z67pUzrAW7zZlCMs0G lDZFt07Brij3pE5P1L3qMYS8FPwWrlJZQutO5E2Z02VVDMHahM4DX6bmZ1aApgzftw4Q nQaEtf/oR65i9bkUskYJZXIJRJjpBOTB0X8VIdmTSMBAUomwYwvP0/1t/FgcYUxkee01 SdPg== X-Gm-Message-State: AHQUAuYLgc/AxZslyzPzgCMWigfN3DwzjSL6zfqMQX47jENYne5ec0D7 ae4nGUp1RBbOkXcW/pj5PUFtOibElEY= X-Google-Smtp-Source: AHgI3IaQemzPoZ6Xs+uzsFpF8NEp8IxV4AYg/8PnQrycpxDYvAOSipqIfPi2aizj09Rq4mfGckRSTQ== X-Received: by 2002:a5d:878d:: with SMTP id f13mr23389942ion.239.1550712730595; Wed, 20 Feb 2019 17:32:10 -0800 (PST) Received: from pryzbyj (charmander.telsasoft.com. [50.244.222.1]) by smtp.gmail.com with ESMTPSA id c14sm7967774iot.13.2019.02.20.17.32.08 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 20 Feb 2019 17:32:09 -0800 (PST) Received: by pryzbyj (Postfix, from userid 1000) id 061F4800C83; Wed, 20 Feb 2019 19:32:07 -0600 (CST) Date: Wed, 20 Feb 2019 19:32:07 -0600 From: Justin Pryzby To: Gunther Cc: pgsql-performance@lists.postgresql.org Subject: Re: neither CPU nor IO bound, but throttled performance Message-ID: <20190221013207.GW28750@telsasoft.com> References: <1b6d8b15-75eb-f00e-2d16-27f79d81eae7@gusw.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1b6d8b15-75eb-f00e-2d16-27f79d81eae7@gusw.net> User-Agent: Mutt/1.5.23 (2014-03-12) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On Wed, Feb 20, 2019 at 06:32:49PM -0500, Gunther wrote: > Hi, I have an Amazon Linux based Postgresql 11 server here on a t2.medium > EC2 instance. > > Everything flows quite nicely. Except, I don't understand why I can't max > out the CPU or the IO, instead, IO is almost negligible yet the CPU is at > 30% hardly hitting 50%. > avg-cpu: %user %nice %system %iowait %steal %idle 36.41 0.00 3.80 0.00 59.78 > 0.00 Device: rrqm/s wrqm/s r/s w/s rkB/s wkB/s avgrq-sz avgqu-sz await > r_await w_await svctm %util xvda 0.00 0.00 0.00 7.69 0.00 92.31 24.00 0.02 This is unreadable, please try to attach it ? > previously I had hit 100 %util here, that was when I didn't have the tables > so spread out over so many tablespaces. Now I have it spread out like in the > olden days where you spread out your tables over many "spindles", and I did > this here so I could see which tables or indexes would be bottlenecks. What was the old storage configuration and what is it now ? > So how can it be that queries take quite long without the process running at > higher CPU%? You said everything flows nicely, but take a long time, and "throttled", can you show an high-level performance change ? Other than %cpu or %io. Justin