From: | Yan Chunlu <springrider(at)gmail(dot)com> |
---|---|
To: | Craig Ringer <ringerc(at)ringerc(dot)id(dot)au> |
Cc: | Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at>, "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: how could select id=xx so slow? |
Date: | 2012-07-12 05:10:06 |
Message-ID: | CAOA66tGY7K=3aPagXUsmFu+3YXn+5gmM7HvxvoPz7YSk-=6EWA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
after check out the wiki page Maciek mentioned, turns out that heavy
connection also burden the disk hardly.
looks like I am in the vicious circle:
1, slow query cause connection blocked so the client request more
connection.
2, more connection cause high disk io and make even the simplest query slow
and block.
I guess I should optimized those queries first...
On Thu, Jul 12, 2012 at 10:20 AM, Craig Ringer <ringerc(at)ringerc(dot)id(dot)au>wrote:
> On 07/12/2012 08:47 AM, Yan Chunlu wrote:
>
> Really sorry for the lack of information
>
> I shouldn't have grumped like that either, sorry about that.
>
>
> I didn't mention the connections number because I don't think my app is
> that busy, and the large number connections was caused by slow queries.
>
>
> Yep - assumptions are a killer like that.
>
> Now you know to watch your system load with iostat, vmstat, top, etc and
> to monitor your overall load.
>
> --
> Craig Ringer
>
From | Date | Subject | |
---|---|---|---|
Next Message | Daniel Farina | 2012-07-12 06:12:35 | Re: DELETE vs TRUNCATE explanation |
Previous Message | Craig Ringer | 2012-07-12 02:20:26 | Re: how could select id=xx so slow? |