Re: Priority table or Cache table

From: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
To: Haribabu Kommi <kommi(dot)haribabu(at)gmail(dot)com>
Cc: Beena Emerson <memissemerson(at)gmail(dot)com>, Sameer Thakur <samthakur74(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Priority table or Cache table
Date: 2015-08-11 06:43:25
Message-ID: CAA4eK1LRuqvJcEJZQ1c1vKL2XVhPSJwZMVid0C+n=4z15TDePA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Aug 11, 2015 at 11:31 AM, Haribabu Kommi <kommi(dot)haribabu(at)gmail(dot)com>
wrote:

> On Mon, Aug 10, 2015 at 3:09 PM, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
> wrote:
> > On Thu, Aug 6, 2015 at 12:24 PM, Haribabu Kommi <
> kommi(dot)haribabu(at)gmail(dot)com>
> > wrote:
> >
> > What is the configuration for test (RAM of m/c, shared_buffers,
> > scale_factor, etc.)?
>
> Here are the details:
>
> CPU - 16 core, RAM - 252 GB
>
> shared_buffers - 1700MB, buffer_cache_ratio - 70
> wal_buffers - 16MB, synchronous_commit - off
> checkpoint_timeout - 15min, max_wal_size - 5GB.
>
> pgbench scale factor - 75 (1GB)
>
> Load test table size - 1GB
>

It seems that test table can fit easily in shared buffers, I am not sure
this patch will be of benefit for such cases, why do you think it can be
beneficial for such cases?

With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2015-08-11 07:37:21 Re: max_connections and standby server
Previous Message Tom Lane 2015-08-11 06:06:53 Re: max_connections and standby server