Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rSlg6-00Fmus-Gd for pgsql-admin@arkaria.postgresql.org; Wed, 24 Jan 2024 22:25:03 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1rSlg3-009C9G-7A for pgsql-admin@arkaria.postgresql.org; Wed, 24 Jan 2024 22:24:59 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rSlg2-009C7g-S5 for pgsql-admin@lists.postgresql.org; Wed, 24 Jan 2024 22:24:58 +0000 Received: from mout.perfora.net ([74.208.4.196]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rSlg0-003CPP-3r for pgsql-admin@lists.postgresql.org; Wed, 24 Jan 2024 22:24:57 +0000 Received: from [192.168.0.142] ([73.171.48.12]) by mrelay.perfora.net (mreueus004 [74.208.5.2]) with ESMTPSA (Nemesis) id 1M73XX-1rRwj93MvH-008aML; Wed, 24 Jan 2024 23:24:48 +0100 Subject: Re: Database log in To: "David G. Johnston" Cc: "Heckler, Kim M" , "pgsql-admin@lists.postgresql.org" References: From: MichaelDBA Message-ID: Date: Wed, 24 Jan 2024 17:24:46 -0500 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 PostboxApp/7.0.60 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/alternative; boundary="------------A0657C08550B3393FFB0EEF1" Content-Language: en-US X-Provags-ID: V03:K1:C+ihsvfrPeu5F+yh+1ZYx6k6OPAFuLtB4fdeWrg+BLs3x6SZlTW tlXsNDn1mDwGOaoKSCR9xkpoLq2eEk7X+5yotMJo8wZSgzAo8MG0XTXIJJiWw70Rp8N5zOd aL2DFp93I93uG6R+D6Au9piPJmDjBAyO1CXPt9yB5fp69WFeyyxBNibvXYLFYHIKef6Nwrl svKlxS/YNOZSONgpaUkJw== X-Spam-Flag: NO UI-OutboundReport: notjunk:1;M01:P0:s1XBff+VwJg=;IwIl0qJJ4Wx8U85uRhE2XKM23MS hAucTQrUrzW1yl80xEIalLPaXaRAxHzp5jsrbHKlkZiFMyB5k9HOYfKWAFeRTStdRhsIxt7bS rxv32w67a3zJE5F5HKT55HuNcBMeotqqd/5MHW9xsieAPUTzVMlNi7YaUK5AGicG28834wjBg 7ndx7M0+Ag47jh3hdloxlDeX8obC6s2tJe+Fxqh5ta4YtH0sJQF3Ke1dblTRtqFMxRJj8W9Bw +jj3LaWvrl4wgePdIcRhcSp5vksqt06s5a1pHpw4GBPuV6Tl9gouyoj/9/HGXJfEI2lQsx/zl 0hEKsXa9reNkHY8jM7cWTkIBFBbPDVylZ7BKWWFsa4v7dY5Gdwm/2nYCbyMEN8neZ2XhqwWG8 dMpLvawwsvOKp42DdiaA+JYDJUtZqU0hNJlF1JLpJKkNE4zXbICZm0EeExpPPN7hA1QsEUmkK sQmwRAbIoFfeUuDOAnHtAx475RiKNz8sodmrbV3zhQm6eOvRljflQWdyLRqkfYHiOYmAxLsx3 cKSIsIZXU4f48ThwHZavvvpK8Bt5B3y/mQnDw+OE3yC8gDHTPHpx3lzqCzd28l044fL44/pdY 0EKzxy4vzthLEI26frfdraWacHBdLjkL1nvun66I0KoXMfBPFlmS0F1NOMwkoXtIuivSz3Nne JI7fOVgcUNIlWC5hz37OTtnd/LtnhhSJYgM82wLvLmShwmeiRbgSnem3jrBTP+pm2YAjwnwDZ /7iUswUEXfGKTyz55/1UeydVV/TAcHgbYWLD1/sM6zy0Sv2/B9dXXC+8ebwMZrOh4ZYQ5XXT7 dBUTwRgINVykgKJLYnBesbPJW6mIbEYigPG5j00zflLecjBgYrLcIjKPlXA73UHMNgvSS3Yug N5HzYBbOg/wRMvw== List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk This is a multi-part message in MIME format. --------------A0657C08550B3393FFB0EEF1 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit 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 > > 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. > --------------A0657C08550B3393FFB0EEF1 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit 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> 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.


--------------A0657C08550B3393FFB0EEF1--