Re: [PERFORM] Very slow inner join query Unacceptable latency.

From: Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>
To: fburgess(at)radiantblue(dot)com
Cc: Jaime Casanova <jaime(at)2ndquadrant(dot)com>, psql performance list <pgsql-performance(at)postgresql(dot)org>, Postgres General <pgsql-general(at)postgresql(dot)org>
Subject: Re: [PERFORM] Very slow inner join query Unacceptable latency.
Date: 2013-05-24 22:03:39
Message-ID: CAOR=d=2i4oJmqoQ4h9NVoTocqfX7uVf1aCZ=SHRr0XMH9uR8cg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-performance

On Fri, May 24, 2013 at 3:44 PM, <fburgess(at)radiantblue(dot)com> wrote:

> Total runtime: 1606.728 ms 1.6 seconds <- very good response time
> improvement
>
> (7 rows)
>
> Questions:
>
> Any concerns with setting these conf variables you recommended; work_mem,
> random_page_cost dbserver wide (in postgresql,conf)?
>
> Thanks so much!!!

Yes 500MB is pretty high especially if you have a lot of connections.
Try it with it back down to 16MB and see how it does. Work mem is per
sort so a setting as high as 500MB can exhaust memory on the machine
under heavy load.

--
To understand recursion, one must first understand recursion.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Dan Birken 2013-05-24 23:42:54 pg_receivexlog 9.2 client working with 9.1 server?
Previous Message fburgess 2013-05-24 21:44:28 Re: [PERFORM] Very slow inner join query Unacceptable latency.

Browse pgsql-performance by date

  From Date Subject
Next Message aup20 2013-05-25 13:46:24 Reporting query failing
Previous Message fburgess 2013-05-24 21:44:28 Re: [PERFORM] Very slow inner join query Unacceptable latency.