Re: slower connect from hostnossl clients

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: slower connect from hostnossl clients
Date: 2016-06-07 10:18:31
Message-ID: CABUevEz5qRmq4EbYsBZ+uJfg_3_ap361ZQtgbH_eF+2j6P0zag@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Jun 7, 2016 at 11:31 AM, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
wrote:

>
>
> 2016-06-07 11:29 GMT+02:00 Magnus Hagander <magnus(at)hagander(dot)net>:
>
>>
>>
>> On Tue, Jun 7, 2016 at 11:24 AM, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
>> wrote:
>>
>>> Hi
>>>
>>> I am testing speed of connection to Postgres.
>>>
>>> The ssl connection is slower, and it is expected. But when I configure
>>> pg_hba.conf to disable ssl via hostnossl, then ssl is not used, but the
>>> speed is similar to ssl.
>>>
>>> Is it expected behave?
>>>
>>>
>> That's definitely not expected behavior. hostnossl should turn off ssl
>> which should turn off the overhead completely. Does it make a difference if
>> you also disable it from the client side?
>>
>
> When I explicitly disabled ssl, then I seen significantly less time
>
>
Intersting. Can you check with a network trace that it actually turns off
ssl, so nothing is broken there?

One thing that could be taking the time is an extra roundtrip -- e.g. it
tries to connect with ssl fails and retries without. A network trace should
also make this obvious, and can hopefully show you exactly where in the
connection the time is spent.

--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Langote 2016-06-07 10:37:09 Re: [sqlsmith] Failed assertion in postgres_fdw/deparse.c:1116
Previous Message Ashutosh Bapat 2016-06-07 10:13:36 Re: [sqlsmith] Failed assertion in postgres_fdw/deparse.c:1116