Re: vacuum performance on insert - Mailing list pgsql-performance

From Kevin Grittner
Subject Re: vacuum performance on insert
Date
Msg-id 4C5FC469020000250003435F@gw.wicourts.gov
Whole thread Raw
In response to Re: vacuum performance on insert  (Sean Chen <zyschen@gmail.com>)
List pgsql-performance
Sean Chen <zyschen@gmail.com> wrote:

> Now from what you mentioned below, do you know what's the cost of
> postgres requesting new disk space from OS?

Depending on your OS and its version, your file system, your mount
options, and your disk subsystem (and its firmware revision), there
could be various effects -- the one likely to be biting you is write
barriers.  When you allocate additional space from the OS, and it
extends a file or creates a new file, there might be a write barrier
to ensure that the file system catalog entries are persisted.  This
could cause all writes (and possibly even reads) to pause until the
data is written to disk.

That's just a guess, of course.   If you have a profiler you can run
you might be able to pin it down with that.

-Kevin

pgsql-performance by date:

Previous
From: Yeb Havinga
Date:
Subject: Re: Completely un-tuned Postgresql benchmark results: SSD vs desktop HDD
Next
From: Scott Carey
Date:
Subject: Re: Completely un-tuned Postgresql benchmark results: SSD vs desktop HDD