| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Peter Geoghegan <pg(at)bowt(dot)ie> |
| Cc: | David Rowley <dgrowleyml(at)gmail(dot)com>, "ldh(at)laurent-hasson(dot)com" <ldh(at)laurent-hasson(dot)com>, 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 16:42:02 |
| Message-ID: | 787780.1626972122@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Peter Geoghegan <pg(at)bowt(dot)ie> writes:
> On Thu, Jul 22, 2021 at 9:21 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Yeah, I should have said "2GB plus palloc slop". It doesn't surprise
>> me a bit that we seem to be eating another 20% on top of the nominal
>> limit.
> MAX_KILOBYTES is the max_val for the work_mem GUC itself, and has been
> for many years.
Right. The point here is that before v13, hash aggregation was not
subject to the work_mem limit, nor any related limit. If you did an
aggregation requiring more than 2GB-plus-slop, it would work just fine
as long as your machine had enough RAM. Now, the performance sucks and
there is no knob you can turn to fix it. That's unacceptable in my book.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2021-07-22 16:53:21 | Re: Big performance slowdown from 11.2 to 13.3 |
| Previous Message | Justin Pryzby | 2021-07-22 16:41:27 | Re: Big performance slowdown from 11.2 to 13.3 |