From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
---|---|
To: | Lazaro Garcia <lazaro3487(at)gmail(dot)com> |
Cc: | "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: Help bad results with pgbench |
Date: | 2017-04-10 15:56:12 |
Message-ID: | CAOR=d=0R1GOBWQ8PEJf7EAc3wgTUX2MxggkJTLp3GgnGJyp3yQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On Mon, Apr 10, 2017 at 9:48 AM, Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> wrote:
> On Mon, Apr 10, 2017 at 9:09 AM, Lazaro Garcia <lazaro3487(at)gmail(dot)com> wrote:
>> 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
> everything fits in RAM (or most of it) and is there because it's been
> accessed. When you reboot the machine is "warming up" so to speak the
> file system cache. Often just running select * from table is all you
> need to warm them up yourself.
So -i 200 is only a couple of gigs. You should fill up the file system
cache 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.
From | Date | Subject | |
---|---|---|---|
Next Message | Lazaro Garcia | 2017-04-10 16:24:24 | Re: Help bad results with pgbench |
Previous Message | Scott Marlowe | 2017-04-10 15:48:17 | Re: Help bad results with pgbench |