pg.ddx.io pgsql-admin@postgresql.org mailing list archive
help / color / mirror / Atom feedDatabase log in
5+ messages / 4 participants
[nested] [flat]
* Database log in
@ 2024-01-24 21:22 Heckler, Kim M <kim.heckler@nationwide.com>
2024-01-24 21:34 ` Database log in David G. Johnston <david.g.johnston@gmail.com>
0 siblings, 1 reply; 5+ messages in thread
From: Heckler, Kim M @ 2024-01-24 21:22 UTC (permalink / raw)
To: pgsql-admin@lists.postgresql.org <pgsql-admin@lists.postgresql.org>
All,
I am experiencing intermitently, slow, log in times. My connection scenario:
1. Kube pod is hosted in Ohio, in AWS account A.
2. Using psql, a log in attempt is initiated from the pod.
3. RDS Postgres Instance is hosted in Ohio, in account B. host has 8 vCPU and 32 GB of RAM. CPU and IO are not a bottle neck.
4. We experience intermittent log in slowness.
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? How many concurrent logins can the DBMS handle in a short time frame? Can 40 sessions be initiated within 90 seconds? 60 seconds?
Please, I would appreciate debugging suggestions.
Thank you in advance, Kim.
^ permalink raw reply [nested|flat] 5+ messages in thread
* Database log in
2024-01-24 21:22 Database log in Heckler, Kim M <kim.heckler@nationwide.com>
@ 2024-01-24 21:34 ` David G. Johnston <david.g.johnston@gmail.com>
2024-01-24 22:24 ` Re: Database log in MichaelDBA <MichaelDBA@sqlexec.com>
0 siblings, 1 reply; 5+ messages in thread
From: David G. Johnston @ 2024-01-24 21:34 UTC (permalink / raw)
To: Heckler, Kim M <kim.heckler@nationwide.com>; +Cc: pgsql-admin@lists.postgresql.org <pgsql-admin@lists.postgresql.org>
On Wednesday, January 24, 2024, Heckler, Kim M <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.
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: Database log in
2024-01-24 21:22 Database log in Heckler, Kim M <kim.heckler@nationwide.com>
2024-01-24 21:34 ` Database log in David G. Johnston <david.g.johnston@gmail.com>
@ 2024-01-24 22:24 ` MichaelDBA <MichaelDBA@sqlexec.com>
2024-01-25 00:22 ` Re: Database log in Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 1 reply; 5+ messages in thread
From: MichaelDBA @ 2024-01-24 22:24 UTC (permalink / raw)
To: David G. Johnston <david.g.johnston@gmail.com>; +Cc: Heckler, Kim M <kim.heckler@nationwide.com>; pgsql-admin@lists.postgresql.org <pgsql-admin@lists.postgresql.org>
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.
>
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: Database log in
2024-01-24 21:22 Database log in Heckler, Kim M <kim.heckler@nationwide.com>
2024-01-24 21:34 ` Database log in David G. Johnston <david.g.johnston@gmail.com>
2024-01-24 22:24 ` Re: Database log in MichaelDBA <MichaelDBA@sqlexec.com>
@ 2024-01-25 00:22 ` Tom Lane <tgl@sss.pgh.pa.us>
2024-01-25 14:25 ` Re: Database log in Heckler, Kim M <kim.heckler@nationwide.com>
0 siblings, 1 reply; 5+ messages in thread
From: Tom Lane @ 2024-01-25 00:22 UTC (permalink / raw)
To: MichaelDBA <MichaelDBA@sqlexec.com>; +Cc: David G. Johnston <david.g.johnston@gmail.com>; Heckler, Kim M <kim.heckler@nationwide.com>; pgsql-admin@lists.postgresql.org <pgsql-admin@lists.postgresql.org>
MichaelDBA <MichaelDBA@sqlexec.com> writes:
> 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...
Yeah. The OP didn't mention the authentication method in use, but
I could believe some sort of performance glitch if it consults an
external server (for Kerberos, AD, LDAP, etc). Or maybe it's
basically a network problem between client and server.
regards, tom lane
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: Database log in
2024-01-24 21:22 Database log in Heckler, Kim M <kim.heckler@nationwide.com>
2024-01-24 21:34 ` Database log in David G. Johnston <david.g.johnston@gmail.com>
2024-01-24 22:24 ` Re: Database log in MichaelDBA <MichaelDBA@sqlexec.com>
2024-01-25 00:22 ` Re: Database log in Tom Lane <tgl@sss.pgh.pa.us>
@ 2024-01-25 14:25 ` Heckler, Kim M <kim.heckler@nationwide.com>
0 siblings, 0 replies; 5+ messages in thread
From: Heckler, Kim M @ 2024-01-25 14:25 UTC (permalink / raw)
To: pgsql-admin@lists.postgresql.org <pgsql-admin@lists.postgresql.org>
>> MichaelDBA <MichaelDBA@sqlexec.com> writes:
>> > 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...
>>
>> Yeah. The OP didn't mention the authentication method in use, but I could believe some sort of
>> performance glitch if it consults an external server (for Kerberos, AD, LDAP, etc).
>> Or maybe it's basically a network problem between client and server.
>>
>> regards, tom lane
>>
Auth method is local password. The AWS RDS Instance does have Kerberos enable so there is ONE role
that authenticates via AD. I was thinking, maybe, that the local ID was mistakenly trying to authenticate
via AD, failing, and then authenticating locally?? I do have a ticket open with AWS to inquire about this.
Also, I will use strace to gather more info.
Thank you, Kim.
^ permalink raw reply [nested|flat] 5+ messages in thread
end of thread, other threads:[~2024-01-25 14:25 UTC | newest]
Thread overview: 5+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2024-01-24 21:22 Database log in Heckler, Kim M <kim.heckler@nationwide.com>
2024-01-24 21:34 ` David G. Johnston <david.g.johnston@gmail.com>
2024-01-24 22:24 ` MichaelDBA <MichaelDBA@sqlexec.com>
2024-01-25 00:22 ` Tom Lane <tgl@sss.pgh.pa.us>
2024-01-25 14:25 ` Heckler, Kim M <kim.heckler@nationwide.com>
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