| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Andrey Vorobiev <andrey(dot)o(dot)vorobiev(at)gmail(dot)com> |
| Cc: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Performance degradation of inserts when database size grows |
| Date: | 2011-05-23 19:08:16 |
| Message-ID: | BANLkTimtRW-FCxkcO5OqjWmro66FwVo9YQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Tue, May 17, 2011 at 8:45 AM, Andrey Vorobiev
<andrey(dot)o(dot)vorobiev(at)gmail(dot)com> wrote:
> 1. How does database size affect insert performance?
Well, if your database gets bigger, then your indexes will become
deeper, requiring more time to update. But I'm not sure that's your
problem here.
> 2. Why does number of written buffers increase when database size grows?
It normally doesn't.
> 3. How can I further analyze this problem?
Are you actually inserting more user data into these tables, so that
they have more and more rows as time goes by, or are the data files
getting larger out of proportion to the amount of useful data in them?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tomas Vondra | 2011-05-23 19:17:33 | Re: Performance degradation of inserts when database size grows |
| Previous Message | Josh Berkus | 2011-05-23 19:08:07 | Re: reducing random_page_cost from 4 to 2 to force index scan |