Re: dbt2 performance regresses from 9.1.6 to 9.2.1

From: Claudio Freire <klaussfreire(at)gmail(dot)com>
To: Dong Ye <yed(at)vmware(dot)com>
Cc: Ants Aasma <ants(at)cybertec(dot)at>, "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org>
Subject: Re: dbt2 performance regresses from 9.1.6 to 9.2.1
Date: 2012-11-05 14:32:37
Message-ID: CAGTBQpYYuHN8hoxjsWdbaVEqLLz0ns9XSATd80v4u=6SxQ-tBA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On Sun, Nov 4, 2012 at 7:23 PM, Dong Ye <yed(at)vmware(dot)com> wrote:
>> You are using prepared statements, this makes me think that this
>> regression might be due to support for parameter specific plans for
>> prepared statements. [1] Can you run the test on both versions without
>> prepared statements and see if the regressions remains.
>
> Without prepare statement, we got 48837.33 avg notpm with 9.1.6 and 43264.54 avg notpm with 9.2.1.
> notps over time shows the slowdown of 9.2.1 is evident during the entire course of the run.
> Their profiles are posted on http://pgsql.privatepaste.com/b770f72967 (9.1.6) and http://pgsql.privatepaste.com/6fa8b7f174 (9.2.1).

You know... it does look as if 9.2.1 is generating a lot more pressure
into the memory allocator (AllocSetAlloc notably higher).

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Jeff Janes 2012-11-05 16:44:34 Re: Re: Increasing work_mem and shared_buffers on Postgres 9.2 significantly slows down queries
Previous Message Albe Laurenz 2012-11-05 10:52:38 Re: help with too slow query