Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cxc9G-0005n3-RO for pgsql-admin@arkaria.postgresql.org; Mon, 10 Apr 2017 16:26:39 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1cxc9G-0007fz-Dm for pgsql-admin@arkaria.postgresql.org; Mon, 10 Apr 2017 16:26:38 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1cxc7H-00028I-DT for pgsql-admin@postgresql.org; Mon, 10 Apr 2017 16:24:35 +0000 Received: from mail-ua0-x234.google.com ([2607:f8b0:400c:c08::234]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1cxc7F-00071G-1X for pgsql-admin@postgresql.org; Mon, 10 Apr 2017 16:24:34 +0000 Received: by mail-ua0-x234.google.com with SMTP id q26so40611290uaa.0 for ; Mon, 10 Apr 2017 09:24:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-transfer-encoding:thread-index :content-language; bh=NLurvVMsxLzpGnhQYi2Xrrp8idh03oQJ7DGpD19DXRY=; b=VUHK4Snv89JebupnIC+X3MC4jAi5fK9BHijtvU4zxUKzvban6a3Y5s0PDBbL1AH/y0 HpP373WY5mCFQkNWtBMcZBpI3uDieMnsMgYO6PtON+v0BVhrtqfB8a2u0JkQTrVEXRfx DjYUd7yctCHyGp5eCEqxN5UEEzTcakRozyAXXa1sCrAesu9cqiEGjuREUJjZPdl6gV7C T6C6NJp55lVddfShI0iheVmGV2/hk0/A0w+Z825gWZwYeCIKguFIEUtT/QA3BcJqivcH zIIoJ3NSDW4Lqk50ZKUqPV6EfYWlo/EO8H+0my/BqRw/U8XChBNHquaQO6uGoS+bxvNY E5+Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:references:in-reply-to:subject:date :message-id:mime-version:content-transfer-encoding:thread-index :content-language; bh=NLurvVMsxLzpGnhQYi2Xrrp8idh03oQJ7DGpD19DXRY=; b=ObzZmjgPH9vFiF4KmR7I4DPYvhXOZjgsc8lYe/8t+ogInjqBV3s2kYPdiKFj89JrbS fkW3cKb1HuGksb3Hy+uLZ42MODRiLteA+S1aSRQOF9GsF877LLsuX0nm6OYJZCDRExNV u3IxTvWNrmmFzdbi/uT9ck/e4GiduQtXM6Y2Ir+YV6NO0RC+eraplP4OM6MvCJu52Eeo hSbJGGValRY4wE5uo9eE3263ezIFD/NqiPWH88Ep5D4GT+KvyjhrNxUzIlyjG1HMlpqB f5n1xGIIeBYH1BXgunk415VMnAiyrAVLcNvkEVOxM1jLboe3i5eVXVFk6Af/7K2Rvsg4 394A== X-Gm-Message-State: AN3rC/5e/kBCr3DSgMxA9fH6z/HrfQxED/i6xmAk2Sb7PwlvhFavv6VrMgmUZoeo45K2Eg== X-Received: by 10.176.69.170 with SMTP id u39mr1526522uau.107.1491841470921; Mon, 10 Apr 2017 09:24:30 -0700 (PDT) Received: from irylachi ([200.55.161.75]) by smtp.gmail.com with ESMTPSA id q189sm3668704vke.36.2017.04.10.09.24.27 (version=TLS1_2 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Mon, 10 Apr 2017 09:24:30 -0700 (PDT) From: "Lazaro Garcia" To: "'Scott Marlowe'" Cc: References: <003101d2b20c$7d2f4fd0$778def70$@gmail.com> In-Reply-To: Subject: Re: Help bad results with pgbench Date: Mon, 10 Apr 2017 12:24:24 -0400 Message-ID: <003c01d2b216$ec6ee180$c54ca480$@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Outlook 15.0 Thread-Index: AQGx2lWGDORi6gouGgTJzqrUpRlHtgGhaOugAcoPOJ2h5Rwy4A== Content-Language: es-mx X-Pg-Spam-Score: -0.8 (/) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-admin Precedence: bulk Sender: pgsql-admin-owner@postgresql.org Thank you very much for the answer, your righ testing it again durin 30 min= and the tps was increasing over the time. Regards and thank you for the help. -----Mensaje original----- De: Scott Marlowe [mailto:scott.marlowe@gmail.com]=20 Enviado el: lunes, 10 de abril de 2017 11:56 a. m. Para: Lazaro Garcia CC: pgsql-admin@postgresql.org Asunto: Re: [ADMIN] Help bad results with pgbench On Mon, Apr 10, 2017 at 9:48 AM, Scott Marlowe wr= ote: > On Mon, Apr 10, 2017 at 9:09 AM, Lazaro Garcia wro= te: >> Good morning everyone. >> >> I'm having the following problem with pgbench and test again: > > Yeah this is the file system cache warm vs cold. In the first instance=20 > everything fits in RAM (or most of it) and is there because it's been=20 > accessed. When you reboot the machine is "warming up" so to speak the=20 > file system cache. Often just running select * from table is all you=20 > need to warm them up yourself. So -i 200 is only a couple of gigs. You should fill up the file system cach= e pretty fast. Just keep running pgbench and the numbers should climb over time. Or you can look into the pg_prewarm module. https://www.postgresql.org/docs/9.4/static/pgprewarm.html -- To understand recursion, one must first understand recursion. --=20 Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin