Re: Performance Improvement by reducing WAL for Update Operation
От | Amit Kapila |
---|---|
Тема | Re: Performance Improvement by reducing WAL for Update Operation |
Дата | |
Msg-id | CAA4eK1LwOi03NTUuhxy_0CEX5KkFdVxp2th72=iFuX11BKZgBw@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Performance Improvement by reducing WAL for Update Operation (Heikki Linnakangas <hlinnakangas@vmware.com>) |
Ответы |
Re: Performance Improvement by reducing WAL for Update Operation
|
Список | pgsql-hackers |
On Wed, Feb 5, 2014 at 8:50 PM, Heikki Linnakangas <hlinnakangas@vmware.com> wrote: > On 02/05/2014 04:48 PM, Amit Kapila wrote: >> >> I have done one test where there is a large suffix match, but >> not large enough that it can compress more than 75% of string, >> the CPU overhead with wal-update-prefix-suffix-encode-1.patch is >> not much, but there is no I/O reduction as well. > > > Hmm, it's supposed to compress if you save at least 25%, not 75%. Apparently > I got that backwards in the patch... So If I understand the code correctly, the new check should be if (prefixlen + suffixlen < (slen * need_rate) / 100) return false; rather than if (slen - prefixlen - suffixlen > (slen * need_rate) / 100) return false; Please confirm, else any validation for this might not be useful? With Regards, Amit Kapila. EnterpriseDB: http://www.enterprisedb.com
В списке pgsql-hackers по дате отправления: