From: | Wei Shan <weishan(dot)ang(at)gmail(dot)com> |
---|---|
To: | Kay <kay(at)9cloud(dot)us> |
Cc: | pgsql-novice(at)postgresql(dot)org |
Subject: | Re: Diagnosing poor insert performance in production? |
Date: | 2015-06-11 03:26:40 |
Message-ID: | CAFe9ZTqXsnK5W16w3k_uGbbPGiJu_R78xZh0iUJ0ipW=mKkk5Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
Hi,
Could you provide more details please for us to help.
1. table definition
2. insert command
3. explain plan
Thanks!
On 10 June 2015 at 03:20, Kay <kay(at)9cloud(dot)us> wrote:
> Where can I look to if I'm trying to diagnose poor insert performance?
>
> The database is behind a pgbouncer instance receiving on average ~1100
> requests per second. It's read heavy, but has the occasional insert. I'd
> estimate about 20-50 per minute.
>
> In the past few days, we loaded a large amount of rows into the database
> (about 5 million on one table, 5 million on another, etc.) and now insert
> performance is poor on all tables... even tables that didn't get data
> loaded
> into them.
>
> I thought insert performance only went down when you try to concurrently
> insert a lot of data, because each insert has to wait on the other in the
> case of an auto-incrementing index. So I'm kind of lost here.... does
> anyone
> have any clues of what I should be looking at?
>
>
>
> --
> View this message in context:
> http://postgresql.nabble.com/Diagnosing-poor-insert-performance-in-production-tp5853106.html
> Sent from the PostgreSQL - novice mailing list archive at Nabble.com.
>
>
> --
> Sent via pgsql-novice mailing list (pgsql-novice(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-novice
>
--
Regards,
Ang Wei Shan
From | Date | Subject | |
---|---|---|---|
Next Message | Merlin Moncure | 2015-06-11 13:48:26 | Re: Diagnosing poor insert performance in production? |
Previous Message | Norbert Kiam Maclang | 2015-06-10 22:15:00 | Re: Tainted kernel possible caused by postgresql |