Re: [PERFORM] Re: [PERFORM] Re: [PERFORM] Re: [PERFORM] Re: 回复： [PERFORM] PG as in-memory db? How to warm up and re-populate buffers? How to read in all tuples into memory?

pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed

From: Tomas Vondra <tv@fuzzy.cz>
To: Claudio Freire <klaussfreire@gmail.com>
Cc: pgsql-performance@postgresql.org <pgsql-performance@postgresql.org>
Subject: Re: [PERFORM] Re: [PERFORM] Re: [PERFORM] Re: [PERFORM] Re: 回复： [PERFORM] PG as in-memory db? How to warm up and re-populate buffers? How to read in all tuples into memory?
Date: Sat, 03 Mar 2012 01:30:18 +0100
Message-ID: <4F51661A.4090903@fuzzy.cz> (raw)
In-Reply-To: <CAGTBQpYKeMhGMtoX31sL=_Np-VZpDPVYDEoOYYw9ckfvYmYaeA@mail.gmail.com>
References: <CAFcOn28A3dkmCEGsu-7Chi0gH1qAPYcfbSp8op9gswFawS6ECA@mail.gmail.com>
	<CAMkU=1y2ea=ZLT-zqyQpNDuuDiNVuWw7xMgpt6R7oVTrHwHVVQ@mail.gmail.com>
	<CAFcOn28k5=B=EY3WOHF0HYOkcAZqzpS+FvTAXzgfj85PM08Msw@mail.gmail.com>
	<CAMkU=1wG13Ysmy=7_BNZPnaRBX6k7GF94ERyA_6amDXu_7y8dg@mail.gmail.com>
	<1330346798.90731.YahooMailNeo@web30808.mail.mud.yahoo.com>
	<CAFcOn2-cdt2=ikUHs-o0aH9tYkVhLD-DnXfo_EmZpFzVrQXEog@mail.gmail.com>
	<CAGTBQpbUvONS+TjKBpdsctgsgL6VZENRWOjWuJHLZmoamKwgDg@mail.gmail.com>
	<8da9b15646d973a5ee23ba49faeee8fd.squirrel@sq.gransy.com>
	<CAGTBQpZA32ngx=gXQUqr=ciOodY+VxhfCvQJoxDXgC+UryhEKA@mail.gmail.com>
	<347477cf700da0b19ad62b50cae5ae1c.squirrel@sq.gransy.com>
	<CAGTBQpazpgN7Z0CUJGJXYZOFssOU5t6PKBo5BUWr7kcpfDsCpQ@mail.gmail.com>
	<7993f32e79b113a0ca3de4d9e500d106.squirrel@sq.gransy.com>
	<CAGTBQpYq68iLhFWg7AVxdY2tU57vU2ch4m3LE_7UXzP=Uw-bKA@mail.gmail.com>
	<4F501EC0.6070801@fuzzy.cz>
	<CAGTBQpYKeMhGMtoX31sL=_Np-VZpDPVYDEoOYYw9ckfvYmYaeA@mail.gmail.com>

On 2.3.2012 03:05, Claudio Freire wrote:
> On Thu, Mar 1, 2012 at 10:13 PM, Tomas Vondra <tv@fuzzy.cz> wrote:
>>
>> Maybe. I still am not sure how fsync=off affects the eviction in your
>> opinion. I think it does not (or just very remotely) and you were saying
>> the opposite. IMHO the eviction of (dirty) buffers is either very fast
>> or slow, no matter what the fsync setting is.
> 
> I was thinking page cleanup, but if you're confident it doesn't happen
> on a read-only database, I'd have to agree on all your other points.
> 
> I have seen a small amount of writes on a read-only devel DB I work
> with, though. Usually in the order of 100kb/s writes per 10mb/s reads
> - I attributed that to page cleanup. In that case, it can add some
> wait time to fsync, even though it's really a slow volume of writes.
> If you're right, I'm thinking, it may be some other thing... atime
> updates maybe, I'd have to check the filesystem configuration I guess.

I'd guess those writes were caused by hint bits (~ page cleanup, but
that's a one-time thing and should be fixed by VACUUM FREEZE right after
the load). Or maybe it was related to runtime stats (i.e. pgstat).

T.

view thread (13+ messages)

Message-ID: <4F51661A.4090903@fuzzy.cz>
Permalink:  ../4F51661A.4090903@fuzzy.cz/
Also on:    postgresql.org/message-id/4F51661A.4090903@fuzzy.cz

 ·

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: tv@fuzzy.cz, klaussfreire@gmail.com
  Subject: Re: [PERFORM] Re: [PERFORM] Re: [PERFORM] Re: [PERFORM] Re: 回复： [PERFORM] PG as in-memory db? How to warm up and re-populate buffers? How to read in all tuples into memory?
  In-Reply-To: <4F51661A.4090903@fuzzy.cz>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox