From: Laurenz Albe <laurenz.albe@cybertec.at>
To: Phani Prathyush Somayajula <phani.somayajula@pragmaticplay.com>
To: pgsql-admin@lists.postgresql.org <pgsql-admin@lists.postgresql.org>
Subject: Re: Postgres RDS DB Parameters ::INSTANCE CLASS : db.m6id.2xlarge
Date: Tue, 18 Jun 2024 13:40:32 +0200
Message-ID: <e724e250c37c61ce3ac33eeb734e6c3f25f6db89.camel@cybertec.at> (raw)
In-Reply-To: <AS4PR10MB55452ECA456BF214261EB8398DCE2@AS4PR10MB5545.EURPRD10.PROD.OUTLOOK.COM>
References: <MAXPR01MB3328F773227E6C76B06CF21BFC22A@MAXPR01MB3328.INDPRD01.PROD.OUTLOOK.COM>
<AS4PR10MB55453EC83E81241722755F8E8D0E2@AS4PR10MB5545.EURPRD10.PROD.OUTLOOK.COM>
<AS4PR10MB55452ECA456BF214261EB8398DCE2@AS4PR10MB5545.EURPRD10.PROD.OUTLOOK.COM>
On Tue, 2024-06-18 at 10:38 +0000, Phani Prathyush Somayajula wrote:
> I have an AWS RDS instance
>
> We are seeing a lot of CPU consumption where we’re load testing our application.
> The query which is taking a lot of time is running less than 1ms if I run through
> my psql client on the server and is taking 162ms if I run it from dBeaver.
>
> I just want to analyse if the parameters that I set are optimal to the application or not.
I don't think that twiddling the parameters will make a lot of difference there.
The exception could be if you are retrieving results with a cursor; then setting
"cursor_tuple_fraction" to 1 could make a difference.
Other than that, you should use auto_explain with "auto_explain.log_analyze = on"
and "auto_explain.log_buffers = on" to capture an execution plan from the slow
execution with DBeaver or your application. Examining that plan should show what
is going on.
Yours,
Laurenz Albe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: laurenz.albe@cybertec.at, phani.somayajula@pragmaticplay.com, pgsql-admin@lists.postgresql.org
Subject: Re: Postgres RDS DB Parameters ::INSTANCE CLASS : db.m6id.2xlarge
In-Reply-To: <e724e250c37c61ce3ac33eeb734e6c3f25f6db89.camel@cybertec.at>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox