Date: Tue, 19 Apr 2022 16:04:21 -0500
From: Justin Pryzby <pryzby@telsasoft.com>
To: Sbob <sbob@quadratum-braccas.com>
Cc: pgsql-performance@lists.postgresql.org
Subject: Re: significant jump in sql statement timing for on server vs a
 remote connection
Message-ID: <20220419210421.GL26620@telsasoft.com>
References: <ddbdea4b-f071-c0fd-d645-2724f489bc77@quadratum-braccas.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <ddbdea4b-f071-c0fd-d645-2724f489bc77@quadratum-braccas.com>
User-Agent: Mutt/1.9.4 (2018-02-28)
Archived-At: 
 <https://www.postgresql.org/message-id/20220419210421.GL26620%40telsasoft.com>
Precedence: bulk

On Tue, Apr 19, 2022 at 03:00:09PM -0600, Sbob wrote:
> We are debugging a sql performance issue. We have a sql file with 50,000
> simple select statements in it. If I run the file locally it completes in
> less than 15sec.  If I force the local connection to be a tcp/ip connection
> via psql -h and I get approximately the same results, 15 - 16sec.
> 
> 
> However if we move the file to another server in the same network and run
> with a psql -h then it runs for more than 10min. Are there any postgres
> specific issues / settings / connection overhead  we should look at? Or is
> this simply a network issue and fully outside the scope of the postgres
> database?

What OS ?  What kind of authentication are you using ?
Is there a connection pooler involved ?  Did you try like that ?

Did you test how long it takes to run 10k empty statements locally vs remotely ?
time yes 'SELECT;' |head -9999 |psql ... >/dev/null

-- 
Justin