RE: Big performance slowdown from 11.2 to 13.3
ldh@laurent-hasson.com <ldh@laurent-hasson.com>
From: "ldh@laurent-hasson.com" <ldh@laurent-hasson.com>
To: Justin Pryzby <pryzby@telsasoft.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, David Rowley <dgrowleyml@gmail.com>, Peter
Geoghegan <pg@bowt.ie>, "pgsql-performance@postgresql.org" <pgsql-performance@postgresql.org>
Date: 2021-07-22T16:30:00Z
Lists: pgsql-performance
-----Original Message----- From: Justin Pryzby <pryzby@telsasoft.com> Sent: Thursday, July 22, 2021 12:23 To: ldh@laurent-hasson.com Cc: Tom Lane <tgl@sss.pgh.pa.us>; David Rowley <dgrowleyml@gmail.com>; Peter Geoghegan <pg@bowt.ie>; pgsql-performance@postgresql.org Subject: Re: Big performance slowdown from 11.2 to 13.3 On Thu, Jul 22, 2021 at 04:16:34PM +0000, ldh@laurent-hasson.com wrote: > Is it fair then to deduce that the total memory usage would be 2,400,305kB + 126,560kB? Is this what under the covers V11 is consuming more or less? It might be helpful to know how much RAM v11 is using. Could you run the query with log_executor_stats=on; client_min_messages=debug; The interesting part is this: ! 7808 kB max resident size -- Justin ------------------------------------------- Hello Justin, > log_executor_stats=on; client_min_messages=debug; Would the results then come in EXPLAIN or would I need to pick something up from the logs? Thank you, Laurent.
Commits
-
Get rid of artificial restriction on hash table sizes on Windows.
- b154ee63bb65 14.0 landed
- 2b8f3f5a7c0e 13.4 landed
- 28d936031a86 15.0 landed