| From: | Peter Geoghegan <peter(at)2ndquadrant(dot)com> |
|---|---|
| To: | Simon Windsor <simon(dot)windsor(at)cornfield(dot)me(dot)uk> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Postgres performance and the Linux scheduler |
| Date: | 2011-06-16 18:20:24 |
| Message-ID: | BANLkTikL4aijPmS5VsCuQqBnUgkKr8s=JA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 16 June 2011 19:10, Simon Windsor <simon(dot)windsor(at)cornfield(dot)me(dot)uk> wrote:
> Can the performance of Postgres be boosted, especially on busy systems,
> using the none default DEADLINE Scheduler?
Probably, but it's a controversial area, and if you want to speed up a
busy system, it would be almost the last thing to look at. Changing
read-ahead settings would be almost the first thing to look at, as
ways of improving the performance of Postgres by tweaking the
operating system go. Increasing this parameter from the default is
often very effective at speeding up sequential scans.
--
Peter Geoghegan http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training and Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alban Hertroys | 2011-06-16 18:21:08 | Re: Constraint to ensure value does NOT exist in another table? |
| Previous Message | Simon Windsor | 2011-06-16 18:10:05 | Postgres performance and the Linux scheduler |