| From: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
|---|---|
| To: | Amit kapila <amit(dot)kapila(at)huawei(dot)com> |
| Cc: | "pgsql-hackers(at)postgreSQL(dot)org" <pgsql-hackers(at)postgreSQL(dot)org> |
| Subject: | Re: [WIP] Performance Improvement by reducing WAL for Update Operation |
| Date: | 2012-08-27 12:28:19 |
| Message-ID: | 503B67E3.7060405@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 27.08.2012 15:18, Amit kapila wrote:
> I have implemented the WAL Reduction Patch for the case of HOT Update as pointed out by Simon and Robert. In this patch it only goes for Optimized WAL in case of HOT Update with other restrictions same as in previous patch.
>
> The performance numbers for this patch are attached in this mail. It has improved by 90% if the page has fillfactor 80.
>
> Now going forward I have following options:
> a. Upload the patch in Open CF for WAL Reduction which contains reductution for HOT and non-HOT updates.
> b. Upload the patch in Open CF for WAL Reduction which contains reductution for HOT updates.
> c. Upload both the patches as different versions.
Let's do it for HOT updates only. Simon & Robert made good arguments on
why this is a bad idea for non-HOT updates.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dirk Lutzebäck | 2012-08-27 12:31:15 | hunspell and tsearch2 ? |
| Previous Message | Amit kapila | 2012-08-27 12:18:46 | Re: [WIP] Performance Improvement by reducing WAL for Update Operation |