From: | Peter Geoghegan <pg(at)heroku(dot)com> |
---|---|
To: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Speed up Clog Access by increasing CLOG buffers |
Date: | 2015-09-21 01:04:28 |
Message-ID: | CAM3SWZRWJp05QvwPtuDL4xmixuYcBeq2ChVZpgwJZdZ_ncGDYQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Aug 31, 2015 at 9:49 PM, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> wrote:
> Increasing CLOG buffers to 64 helps in reducing the contention due to second
> reason. Experiments revealed that increasing CLOG buffers only helps
> once the contention around ProcArrayLock is reduced.
There has been a lot of research on bitmap compression, more or less
for the benefit of bitmap index access methods.
Simple techniques like run length encoding are effective for some
things. If the need to map the bitmap into memory to access the status
of transactions is a concern, there has been work done on that, too.
Byte-aligned bitmap compression is a technique that might offer a good
trade-off between compression clog, and decompression overhead -- I
think that there basically is no decompression overhead, because set
operations can be performed on the "compressed" representation
directly. There are other techniques, too.
Something to consider. There could be multiple benefits to compressing
clog, even beyond simply avoiding managing clog buffers.
--
Peter Geoghegan
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2015-09-21 01:17:00 | Re: RFC: replace pg_stat_activity.waiting with something more descriptive |
Previous Message | Stephen Frost | 2015-09-20 21:57:41 | Re: CREATE POLICY and RETURNING |