From: MichaelDBA <MichaelDBA@sqlexec.com>
To: David G. Johnston <david.g.johnston@gmail.com>
Cc: Heckler, Kim M <kim.heckler@nationwide.com>
Cc: pgsql-admin@lists.postgresql.org <pgsql-admin@lists.postgresql.org>
Subject: Re: Database log in
Date: Wed, 24 Jan 2024 17:24:46 -0500
Message-ID: <c3c3ed0c-cf0f-3030-8610-00b055c17d41@sqlexec.com> (raw)
In-Reply-To: <CAKFQuwZGywd1hUbvgq+4j9eCEZWtDYL7c4WFofy01ygOXtjYiw@mail.gmail.com>
References: <SA1PR07MB8484F96961B8B73832FB3F4B867B2@SA1PR07MB8484.namprd07.prod.outlook.com>
<CAKFQuwZGywd1hUbvgq+4j9eCEZWtDYL7c4WFofy01ygOXtjYiw@mail.gmail.com>
I don't have a problem with hundreds or thousands of logins per minute
on RDS or bare metal, even with only 8 CPUs and 32GB RAM. There is
something else in play here...
David G. Johnston wrote on 1/24/2024 4:34 PM:
> On Wednesday, January 24, 2024, Heckler, Kim M
> <kim.heckler@nationwide.com <mailto:kim.heckler@nationwide.com>> wrote:
>
> My questions are around what happens at log in time; what are the
> sequence of events? Also, how much “stress” does log in have to
> the DBMS?
>
> A decent amount.
>
> How many concurrent logins can the DBMS handle in a short time
> frame? Can 40 sessions be initiated within 90 seconds? 60 seconds?
>
> It depends.
>
> Please, I would appreciate debugging suggestions.
>
> Don’t? At this point you’ve probably hit the point where connection
> pools are the best way forward. Especially since 8 is much less than 40.
>
> David J.
>
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: MichaelDBA@sqlexec.com, david.g.johnston@gmail.com, kim.heckler@nationwide.com, pgsql-admin@lists.postgresql.org
Subject: Re: Database log in
In-Reply-To: <c3c3ed0c-cf0f-3030-8610-00b055c17d41@sqlexec.com>
* 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