| From: | MichaelDBA <MichaelDBA(at)sqlexec(dot)com> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | "Heckler, Kim M" <kim(dot)heckler(at)nationwide(dot)com>, "pgsql-admin(at)lists(dot)postgresql(dot)org" <pgsql-admin(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Database log in |
| Date: | 2024-01-24 22:24:46 |
| Message-ID: | c3c3ed0c-cf0f-3030-8610-00b055c17d41@sqlexec.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
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(dot)heckler(at)nationwide(dot)com <mailto:kim(dot)heckler(at)nationwide(dot)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.
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2024-01-25 00:22:13 | Re: Database log in |
| Previous Message | David G. Johnston | 2024-01-24 21:34:44 | Database log in |