You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Bryan Call (JIRA)" <ji...@apache.org> on 2014/09/17 00:41:35 UTC

[jira] [Comment Edited] (TS-3080) OpenSSL implementation of TLS session cache is very slow.

    [ https://issues.apache.org/jira/browse/TS-3080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14136400#comment-14136400 ] 

Bryan Call edited comment on TS-3080 at 9/16/14 10:41 PM:
----------------------------------------------------------

In production we were using the OpenSSL session cache and were doing ~5k qps.   How are you determining it is a locking issue?


was (Author: bcall):
In production we were using the OpenSSL session cache and were going ~5k qps.   How are you determining it is a locking issue?

> OpenSSL implementation of TLS session cache is very slow.
> ---------------------------------------------------------
>
>                 Key: TS-3080
>                 URL: https://issues.apache.org/jira/browse/TS-3080
>             Project: Traffic Server
>          Issue Type: Bug
>          Components: Core, SSL
>            Reporter: Brian Geffon
>            Assignee: Brian Geffon
>
> The OpenSSL implementation of TLS session caching is very slow, we attempted to use it and it's locking and blows up at only a few hundred QPS. I'm going to develop a new TLS session cache in TS that is more performant under highload.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)