Re: Performance Improvement by reducing WAL for Update Operation
Robert Haas <robertmhaas@gmail.com>
From: Robert Haas <robertmhaas@gmail.com>
To: Amit Kapila <amit.kapila16@gmail.com>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>,
Mike Blackwell <mike.blackwell@rrd.com>
Date: 2014-01-28T03:39:25Z
Lists: pgsql-hackers
Attachments
- pgrb-v5 test.ods (application/vnd.oasis.opendocument.spreadsheet)
On Mon, Jan 27, 2014 at 12:03 PM, Amit Kapila <amit.kapila16@gmail.com> wrote: >> I think that's a good thing to try. Can you code it up? > > I have tried to improve algorithm in another way so that we can get > benefit of same chunks during find match (something similar to lz). > The main change is to consider chunks at fixed boundary (4 byte) > and after finding match, try to find if there is a longer match than > current chunk. While finding longer match, it still takes care that > next bigger match should be at chunk boundary. I am not > completely sure about the chunk boundary may be 8 or 16 can give > better results. > > I think now we can once run with this patch on high end m/c. Here are the results I got on the community PPC64 box. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
Commits
-
Flush stderr and stdout in isolation tester.
- 63d283ecd0bc 9.3.0 cited