Re: checkpointer continuous flushing

From: Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, PostgreSQL Developers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: checkpointer continuous flushing
Date: 2016-03-22 09:52:55
Message-ID: alpine.DEB.2.10.1603221045000.8198@sto
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


> WRT tablespaces: What I'm planning to do, unless somebody has a better
> proposal, is to basically rent two big amazon instances, and run pgbench
> in parallel over N tablespaces. Once with local SSD and once with local
> HDD storage.

Ok.

Not sure how to control that table spaces are actually on distinct
dedicated disks with VMs, but this is the idea.

To emphasize potential bad effects without having to build too large a
host and involve too many table spaces, I would suggest to reduce
significantly the "checkpoint_flush_after" setting while running these
tests.

--
Fabien.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2016-03-22 09:53:03 Re: checkpointer continuous flushing
Previous Message Alexander Korotkov 2016-03-22 09:50:07 Re: WIP: Access method extendability