| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "ldh(at)laurent-hasson(dot)com" <ldh(at)laurent-hasson(dot)com> |
| Cc: | David Rowley <dgrowleyml(at)gmail(dot)com>, 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 15:45:02 |
| Message-ID: | 784576.1626968702@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
"ldh(at)laurent-hasson(dot)com" <ldh(at)laurent-hasson(dot)com> writes:
> So, I went possibly nuclear, and still no cigar. Something's not right.
> - hash_mem_multiplier = '10'
> - work_mem = '1GB'
> The results are
> Batches: 5 Memory Usage: 2,449,457kB Disk Usage: 105,936kB
> Execution Time: 1,837,126.766 ms
> It's still spilling to disk and seems to cap at 2.5GB of memory usage in spite of configuration.
That is ... weird. Maybe you have found a bug in the spill-to-disk logic;
it's quite new after all. Can you extract a self-contained test case that
behaves this way?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2021-07-22 15:56:49 | Re: Big performance slowdown from 11.2 to 13.3 |
| Previous Message | ldh@laurent-hasson.com | 2021-07-22 15:00:33 | RE: Big performance slowdown from 11.2 to 13.3 |