Re: Performance Improvement by reducing WAL for Update Operation - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: Performance Improvement by reducing WAL for Update Operation
Date
Msg-id CA+U5nM+E-+UV2X3qrfiFjXFbenxL+aWyNMW0Lfp24qVLnBJ+ug@mail.gmail.com
Whole thread Raw
In response to Re: Performance Improvement by reducing WAL for Update Operation  (Amit kapila <amit.kapila@huawei.com>)
Responses Re: Performance Improvement by reducing WAL for Update Operation
Re: Performance Improvement by reducing WAL for Update Operation
List pgsql-hackers
On 9 January 2013 08:05, Amit kapila <amit.kapila@huawei.com> wrote:

> Update patch contains handling of below Comments

Thanks


> Test results with modified pgbench (1800 record size) on the latest patch:
>
> -Patch-             -tps@-c1-     -WAL@-c1-      -tps@-c2-      -WAL@-c2-
> Head                831           4.17 GB        1416           7.13 GB
> WAL modification    846           2.36 GB        1712           3.31 GB
>
> -Patch-             -tps@-c4-     -WAL@-c4-      -tps@-c8-      -WAL@-c8-
> Head                2196          11.01 GB       2758           13.88 GB
> WAL modification    3295           5.87 GB       5472            9.02 GB

And test results on normal pgbench?

-- Simon Riggs                   http://www.2ndQuadrant.com/PostgreSQL Development, 24x7 Support, Training & Services



pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: Re: patch submission: truncate trailing nulls from heap rows to reduce the size of the null bitmap [Review]
Next
From: Andres Freund
Date:
Subject: [PATCH 2/2] use pg_malloc instead of an unchecked malloc in pg_resetxlog