From: | Kay <kay(at)9cloud(dot)us> |
---|---|
To: | pgsql-novice(at)postgresql(dot)org |
Subject: | Diagnosing poor insert performance in production? |
Date: | 2015-06-09 19:20:40 |
Message-ID: | 1433877640749-5853106.post@n5.nabble.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
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.
From | Date | Subject | |
---|---|---|---|
Next Message | bobt_1234 | 2015-06-10 18:19:36 | Cannot view tables when connecting to PostgreSQL from SQL Developer |
Previous Message | Albe Laurenz | 2015-06-09 08:32:23 | Re: Tainted kernel possible caused by postgresql |