Re: vacuum performance on insert

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Sean Chen" <zyschen(at)gmail(dot)com>
Cc: <pgsql-performance(at)postgresql(dot)org>,"Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: vacuum performance on insert
Date: 2010-08-09 14:03:37
Message-ID: 4C5FC469020000250003435F@gw.wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Sean Chen <zyschen(at)gmail(dot)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

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Scott Carey 2010-08-09 16:49:50 Re: Completely un-tuned Postgresql benchmark results: SSD vs desktop HDD
Previous Message Yeb Havinga 2010-08-08 10:12:07 Re: Completely un-tuned Postgresql benchmark results: SSD vs desktop HDD