On Wednesday, January 09, 2013 4:57 PM Simon Riggs wrote:
> On 9 January 2013 08:05, Amit kapila <amit(dot)kapila(at)huawei(dot)com> wrote:
> > Update patch contains handling of below Comments
> > Test results with modified pgbench (1800 record size) on the latest
> > -Patch- -tps(at)-c1- -WAL(at)-c1- -tps(at)-c2- -
> > Head 831 4.17 GB 1416 7.13
> > WAL modification 846 2.36 GB 1712 3.31
> > -Patch- -tps(at)-c4- -WAL(at)-c4- -tps(at)-c8- -
> > Head 2196 11.01 GB 2758 13.88
> > WAL modification 3295 5.87 GB 5472 9.02
> And test results on normal pgbench?
As there was no gain for original pgbench as was shown in performance
readings, so I thought it is not mandatory.
However I shall run for normal pgbench as it should not lead any further dip
in normal pgbench.
Thanks for pointing.
In response to
pgsql-hackers by date
|Next:||From: Simon Riggs||Date: 2013-01-09 12:14:34|
|Subject: Re: Re: patch submission: truncate trailing nulls from heap
rows to reduce the size of the null bitmap [Review]|
|Previous:||From: Amit Kapila||Date: 2013-01-09 12:06:14|
|Subject: Re: Re: patch submission: truncate trailing nulls from heap rows to reduce the size of the null bitmap [Review]|