From: | David Rowley <dgrowleyml(at)gmail(dot)com> |
---|---|
To: | "ldh(at)laurent-hasson(dot)com" <ldh(at)laurent-hasson(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Peter Geoghegan <pg(at)bowt(dot)ie>, Justin Pryzby <pryzby(at)telsasoft(dot)com>, "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: Big performance slowdown from 11.2 to 13.3 |
Date: | 2021-07-22 04:43:51 |
Message-ID: | CAApHDvqoF7y7SQjGT=940njnAd_CUcUG6oRYChcP_+eJyuNiug@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On Thu, 22 Jul 2021 at 16:37, ldh(at)laurent-hasson(dot)com
<ldh(at)laurent-hasson(dot)com> wrote:
> Seems like no cigar ☹ See plan pasted below. I changed the conf as follows:
> - hash_mem_multiplier = '2'
> - work_mem = '1GB'
> Batches: 5 Memory Usage: 2400305kB Disk Usage: 126560kB
You might want to keep going higher with hash_mem_multiplier until you
see no "Disk Usage" there. As mentioned, v11 didn't spill to disk and
just used all the memory it pleased. That was a bit dangerous as it
could result in OOM, so it was fixed.
David
From | Date | Subject | |
---|---|---|---|
Next Message | Kamil Frydel | 2021-07-22 11:32:51 | Partitioned table statistics vs autoanalyze |
Previous Message | ldh@laurent-hasson.com | 2021-07-22 04:37:41 | RE: Big performance slowdown from 11.2 to 13.3 |