Re: Re: patch submission: truncate trailing nulls from heap rows to reduce the size of the null bitmap [Review]

From: Amit Kapila <amit(dot)kapila(at)huawei(dot)com>
To: "'Kevin Grittner'" <kgrittn(at)mail(dot)com>, "'Simon Riggs'" <simon(at)2ndQuadrant(dot)com>
Cc: <robertmhaas(at)gmail(dot)com>, <josh(at)agliodbs(dot)com>, <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Re: patch submission: truncate trailing nulls from heap rows to reduce the size of the null bitmap [Review]
Date: 2012-12-24 16:57:21
Message-ID: 00bc01cde1f7$be4b4cb0$3ae1e610$@kapila@huawei.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Monday, December 24, 2012 7:58 PM Kevin Grittner wrote:
> Simon Riggs wrote:
>
> > Not really sure about the 100s of columns use case.
> >
> > But showing gain in useful places in these more common cases wins
> > my vote.
> >
> > Thanks for testing. Barring objections, will commit.
>
> Do we have any results on just a plain, old stock pgbench run, with
> the default table definitions?
>
> That would be a reassuring complement to the other tests.

Sever Configuration:
The database cluster will be initialized with locales
COLLATE: C
CTYPE: C
MESSAGES: en_US.UTF-8
MONETARY: en_US.UTF-8
NUMERIC: en_US.UTF-8
TIME: en_US.UTF-8

shared_buffers = 1GB
checkpoint_segments = 255
checkpoint_timeout = 15min

pgbench:
transaction type: TPC-B (sort of)
scaling factor: 75
query mode: simple
number of clients: 8
number of threads: 8
duration: 600 s

Performance: Average of 3 runs of pgbench in tps
9.3devel | with trailing null patch
----------+--------------------------
578.9872 | 573.4980

With Regards,
Amit Kapila.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Dimitri Fontaine 2012-12-24 17:06:44 Re: Feature Request: pg_replication_master()
Previous Message Tom Lane 2012-12-24 16:56:44 Re: buffer assertion tripping under repeat pgbench load