Re: Performance increase with elevator=deadline

From: Gregory Stark <stark(at)enterprisedb(dot)com>
To: "Albe Laurenz" <laurenz(dot)albe(at)wien(dot)gv(dot)at>
Cc: <pgsql-performance(at)postgresql(dot)org>
Subject: Re: Performance increase with elevator=deadline
Date: 2008-04-11 14:47:17
Message-ID: 878wzkh2iy.fsf@oxford.xeocode.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

"Albe Laurenz" <laurenz(dot)albe(at)wien(dot)gv(dot)at> writes:

> This refers to the performance problem reported in
> http://archives.postgresql.org/pgsql-performance/2008-04/msg00052.php
>
> After some time of trial and error we found that changing the I/O scheduling
> algorithm to "deadline" improved I/O performance by a factor 4 (!) for
> this specific load test.

What was the algorithm before?

--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's On-Demand Production Tuning

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Jeff 2008-04-11 15:09:07 Re: Performance increase with elevator=deadline
Previous Message Vivek Khera 2008-04-11 14:41:09 Re: recommendations for web/db connection pooling or DBD::Gofer reviews