Editing OpenSSL (section)

=== Significant performance regressions ===

The reduced support delay of version 1.1.1 mentioned above causes further concerns to users whose workloads are sensitive to performance. Some time after general availability of 3.0, some users started to report serious performance regressions affecting this version in multi-threaded environments, many citing the inefficient use of locks in frequent low-level operations, citing slowdowns from 80 to 400 times.<ref>{{Cite web|url=https://github.com/openssl/openssl/issues/17064|title=Massive performance degradation in OpenSsl 3.0 if used in a heavy multi threaded server application · Issue #17064 · openssl/openssl|website=GitHub|access-date=February 25, 2023|archive-date=December 8, 2024|archive-url=https://web.archive.org/web/20241208114743/https://github.com/openssl/openssl/issues/17064|url-status=live}}</ref><ref>{{Cite web|url=https://github.com/openssl/openssl/issues/17950|title=Performance issue with Openssl 3.0 in multi threaded application when using d2i_x509 · Issue #17950 · openssl/openssl|website=GitHub|access-date=February 25, 2023|archive-date=December 8, 2024|archive-url=https://web.archive.org/web/20241208051208/https://github.com/openssl/openssl/issues/17950|url-status=live}}</ref><ref>{{Cite web|url=https://github.com/openssl/openssl/issues/18814|title=Severe efficiency degradation of credential loading in comparison to 1.1.1 · Issue #18814 · openssl/openssl|website=GitHub|access-date=February 25, 2023|archive-date=December 7, 2024|archive-url=https://web.archive.org/web/20241207231338/https://github.com/openssl/openssl/issues/18814|url-status=live}}</ref><ref>{{Cite web|url=https://github.com/openssl/openssl/issues/20286|title=3.0 performance degraded due to locking · Issue #20286 · openssl/openssl|website=GitHub}}</ref><ref>{{Cite web|url=https://github.com/nodejs/node/issues/43128|title=High cpu usage for outbound ssl requests after upgrading from v16.15.0 to v18.1.0 · Issue #43128 · nodejs/node|website=GitHub|access-date=February 25, 2023|archive-date=December 8, 2024|archive-url=https://web.archive.org/web/20241208011158/https://github.com/nodejs/node/issues/43128|url-status=live}}</ref><ref>{{Cite web|url=https://github.com/openssl/openssl/issues/18472|title=Massive performance degradation in OpenSsl 3.0 FIPS provider · Issue #18472 · openssl/openssl|website=GitHub|access-date=February 25, 2023|archive-date=December 8, 2024|archive-url=https://web.archive.org/web/20241208192721/https://github.com/openssl/openssl/issues/18472|url-status=live}}</ref><ref>{{Cite web|url=https://github.com/openssl/openssl/issues/16791|title=Performance measurements · Issue #16791 · openssl/openssl|website=GitHub|access-date=February 25, 2023|archive-date=December 8, 2024|archive-url=https://web.archive.org/web/20241208124557/https://github.com/openssl/openssl/issues/16791|url-status=live}}</ref><ref>{{Cite web|url=https://github.com/openssl/openssl/issues/15199|title=PEM/DER decoding of PKCS8 RSA private keys are 80 times slower in 3.0 · Issue #15199 · openssl/openssl|website=GitHub|access-date=February 25, 2023|archive-date=December 8, 2024|archive-url=https://web.archive.org/web/20241208060652/https://github.com/openssl/openssl/issues/15199|url-status=live}}</ref> The OpenSSL team has created a meta-issue to try to centralize reports of such massive performance regressions.<ref>{{Cite web|url=https://github.com/openssl/openssl/issues/17627|title=3.0 Performance problems · Issue #17627 · openssl/openssl|website=GitHub|access-date=February 25, 2023|archive-date=December 8, 2024|archive-url=https://web.archive.org/web/20241208073139/https://github.com/openssl/openssl/issues/17627|url-status=live}}</ref> About half of these reporters indicate the impossibility for them to upgrade to 3.0 from earlier versions, adding to the trouble caused by the limited support time left on previous version 1.1.1.