Skip site navigation (1) Skip section navigation (2)

Re: Performance degradation of inserts when database size grows

From: Shaun Thomas <sthomas(at)peak6(dot)com>
To: Andrey Vorobiev <andrey(dot)o(dot)vorobiev(at)gmail(dot)com>
Cc: <pgsql-performance(at)postgresql(dot)org>
Subject: Re: Performance degradation of inserts when database size grows
Date: 2011-05-23 13:30:34
Message-ID: 4DDA617A.6090105@peak6.com (view raw or flat)
Thread:
Lists: pgsql-performance
On 05/17/2011 07:45 AM, Andrey Vorobiev wrote:

> 2011-05-17 18:55:51 NOVST LOG: checkpoint starting: xlog
> 2011-05-17 18:57:20 NOVST LOG: checkpoint complete: wrote 62861 buffers
> (24.0%); 0 transaction log file(s) added, 0 removed, 0 recycled;
> write=89.196 s, sync=0.029 s, total=89.242 s

Increase your checkpoint_segments. If you see "checkpoint starting: 
xlog" instead of "checkpoint starting: time", you don't have enough 
checkpoint segments to handle your writes. Checkpoints *will* degrade 
your throughput.

-- 
Shaun Thomas
OptionsHouse | 141 W. Jackson Blvd. | Suite 800 | Chicago IL, 60604
312-676-8870
sthomas(at)peak6(dot)com

______________________________________________

See  http://www.peak6.com/email_disclaimer.php
for terms and conditions related to this email

In response to

Responses

pgsql-performance by date

Next:From: Aren CambreDate: 2011-05-23 14:06:48
Subject: Re: Postgres refusing to use >1 core
Previous:From: Shaun ThomasDate: 2011-05-23 13:26:11
Subject: Re: [OT]: Confidentiality disclosures in list posts (Was: SORT performance - slow?)

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group