Re: 8.2 is 30% better in pgbench than 8.3

From: "Pavan Deolasee" <pavan(dot)deolasee(at)gmail(dot)com>
To: "Simon Riggs" <simon(at)2ndquadrant(dot)com>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Pavel Stehule" <pavel(dot)stehule(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: 8.2 is 30% better in pgbench than 8.3
Date: 2007-07-23 16:34:05
Message-ID: 2e78013d0707230934y629a2aeerdae4315cb3424947@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 7/23/07, Alvaro Herrera <alvherre(at)commandprompt(dot)com> wrote:
>
>
>
> Certainly it doesn't prevent starvation completely -- really there is no
> way to completely prevent starvation unless you have as many workers as
> you have tables, and one disk for each. What DSM does do is let the big
> tables be vacuumed quickly which makes most of the problem go away.
>
>
>
Frankly I haven't seen DSM results very closely, but DSM can help
us avoid full heap scans (and thats a big thing!), but it can't avoid the
associated index scans and that might limit our ability to vacuum very
large tables frequently.

Thanks,
Pavan

--
Pavan Deolasee
EnterpriseDB http://www.enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Magnus Hagander 2007-07-23 16:43:44 Re: MAXIMUM_ALIGNOF on Windows-32
Previous Message Florian G. Pflug 2007-07-23 16:30:07 Re: Full page images in WAL & Cache Invalidation