Re: Is OpenSSL AES-NI not available in pgcrypto?
| От | Peter Eisentraut |
|---|---|
| Тема | Re: Is OpenSSL AES-NI not available in pgcrypto? |
| Дата | |
| Msg-id | 83bd3e5c-1d7e-0b34-9e93-9fa8ecd0a77e@enterprisedb.com обсуждение исходный текст |
| Ответ на | Is OpenSSL AES-NI not available in pgcrypto? ("agharta82@gmail.com" <agharta82@gmail.com>) |
| Ответы |
Re: Is OpenSSL AES-NI not available in pgcrypto?
|
| Список | pgsql-hackers |
On 02.01.23 17:57, agharta82@gmail.com wrote:
> select pgp_sym_encrypt(data::text, 'pwd') --default to aes128
> from generate_series('2022-01-01'::timestamp, '2022-12-31'::timestamp,
> '1 hour'::interval) data
>
> vs
>
> select pgp_sym_encrypt(data::text, 'pwd','cipher-algo=bf') -- blowfish
> from generate_series('2022-01-01'::timestamp, '2022-12-31'::timestamp,
> '1 hour'::interval) data
>
> In my test both queries execution is similar....aes-128 was expected
> about 5 time faster.
>
> So, why?
>
> Pgcrypto use OpenSSL as backend, so, does it explicit force software aes
> calculation instead of AES-NI cpu ones?
I suspect it is actually using AES hardware support, but all the other
overhead of pgcrypto makes the difference not noticeable.
В списке pgsql-hackers по дате отправления: