pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Grega Bremec <grega.bremec@noviforum.si>
To: eleven <eleven@ludojad.itpp.pl>
Cc: pgsql-performance@postgresql.org
Subject: Re: high load caused by I/O - a hint
Date: Wed, 18 Aug 2004 10:51:54 +0200
Message-ID: <20040818085154.GA27512@elbereth.noviforum.si> (raw)
In-Reply-To: <412310CB.8080908@ludojad.itpp.pl>
References: <412310CB.8080908@ludojad.itpp.pl>

...and on Wed, Aug 18, 2004 at 10:18:19AM +0200, eleven used the keyboard:
> Hello,
> 
> This is not strictly PostgreSQL performance hint, but may be
> helpful to someone with problems like mine.
> 
> As I earlier posted, I was experiencing very high load average
> on one of my Linux database servers (IBM eServer 345, SCSI disks on LSI 
> Logic controller) caused by I/O bottleneck.
> 
> INSERTs were really slow, even after many days of
> tweaking PostgreSQL configuration. The problem appeared to be
> in the Linux kernel itself - using acpi=ht and noapic boot parameters
> solved my performance problems. Load average dropped below 1.0
> (before, it was as high as ten in peak) and the database
> works much, much faster.

Hello,

Did you try with acpi=noidle? This proved to be of help on many an
occasion before, and you don't have to give up any functionality over
it. It's just that the ACPI BIOS is broken and overloads the system
with idle calls.

Other than that, general guidelines would be, don't combine APM and
ACPI, and rather use proper SMP code for hyperthreaded machines than
just the ACPI CPU enumeration feature.

There's also a new option with 2.6.8.1, called CONFIG_SCHED_SMT that
is supposed to handle some cases SMP code had problems with better,
at the cost of slight overhead in other areas.

My advice would be, if you have an option to choose between APM and
ACPI, go for ACPI. It's the future, it's being developed actively,
it does a whole lot more than APM (that was really only about power
management), and last but not least, I've been using it for four
years on over fifty SMP machines and I never ever had a problem
beyond the scope of what noidle could fix (knocks-on-wood). :)

HTH,
-- 
    Grega Bremec
    Senior Administrator
    Noviforum Ltd., Software & Media
    http://www.noviforum.si/

view thread (4+ messages)  latest in thread

Message-ID: <20040818085154.GA27512@elbereth.noviforum.si>
Permalink:  ../20040818085154.GA27512@elbereth.noviforum.si/
Also on:    postgresql.org/message-id/20040818085154.GA27512@elbereth.noviforum.si

 · 

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-performance@postgresql.org
  Cc: grega.bremec@noviforum.si, eleven@ludojad.itpp.pl
  Subject: Re: high load caused by I/O - a hint
  In-Reply-To: <20040818085154.GA27512@elbereth.noviforum.si>
  References: <412310CB.8080908@ludojad.itpp.pl> <20040818085154.GA27512@elbereth.noviforum.si>

* 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