| From: | Francisco Olarte <folarte(at)peoplecall(dot)com> |
|---|---|
| To: | Bill Moran <wmoran(at)potentialtech(dot)com> |
| Cc: | Tom Smith <tomsmith1989sk(at)gmail(dot)com>, PostgreSQL General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: JSONB performance enhancement for 9.6 |
| Date: | 2015-11-29 12:28:36 |
| Message-ID: | CA+bJJbzRn6eogY6ZEUn+kfBCy9US=Wtvqa-+JvkOVFJr=9UP_Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hi:
On Sun, Nov 29, 2015 at 1:09 PM, Bill Moran <wmoran(at)potentialtech(dot)com> wrote:
> On Sat, 28 Nov 2015 21:27:51 -0500
>> Currently, if I save a large json document with top level keys of thousands
** LARGE **
> The default storage for a JSONB field is EXTENDED. Switching it to
> EXTERNAL will disable compression. You'll have to insert your data over
> again, since this change doesn't alter any existing data, but see
> if that change improves performance.
Good recomendation, but see if it improves AND if it affects other
queries in the system. Turning off compresion CAN decrease the
eficiency ( hit ratio ) of the shared buffers and the cache, IIRC (
but worth testing anyway ).
Francisco Olarte.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Kellerer | 2015-11-29 12:35:06 | Re: JSONB performance enhancement for 9.6 |
| Previous Message | Bill Moran | 2015-11-29 12:09:31 | Re: JSONB performance enhancement for 9.6 |