{"action":"closed","issue":{"url":"https://api.github.com/repos/polarssl/polarssl/issues/168","labels_url":"https://api.github.com/repos/polarssl/polarssl/issues/168/labels{/name}","comments_url":"https://api.github.com/repos/polarssl/polarssl/issues/168/comments","events_url":"https://api.github.com/repos/polarssl/polarssl/issues/168/events","html_url":"https://github.com/polarssl/polarssl/issues/168","id":57531997,"number":168,"title":"tls handshake very slow","user":{"login":"jkarneges","id":521953,"avatar_url":"https://avatars.githubusercontent.com/u/521953?v=3","gravatar_id":"","url":"https://api.github.com/users/jkarneges","html_url":"https://github.com/jkarneges","followers_url":"https://api.github.com/users/jkarneges/followers","following_url":"https://api.github.com/users/jkarneges/following{/other_user}","gists_url":"https://api.github.com/users/jkarneges/gists{/gist_id}","starred_url":"https://api.github.com/users/jkarneges/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jkarneges/subscriptions","organizations_url":"https://api.github.com/users/jkarneges/orgs","repos_url":"https://api.github.com/users/jkarneges/repos","events_url":"https://api.github.com/users/jkarneges/events{/privacy}","received_events_url":"https://api.github.com/users/jkarneges/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":3,"created_at":"2015-02-12T22:47:09Z","updated_at":"2015-02-13T00:49:23Z","closed_at":"2015-02-13T00:49:23Z","body":"Hi,\r\n\r\nI'm using mongrel2 with polarssl 1.3. Earlier I was using 1.3.0, and a few days ago I updated polarssl to 1.3.10. Since the update, I've observed that TLS handshakes seem to be at least 3x slower, and I have a feeling that some blocking code in polarssl is causing extra trouble for mongrel2's single-threaded event-driven engine (based on libtask).\r\n\r\nSorry for not having too many details yet, I'm investigating further now, but I just wanted to throw this out there in case anyone had a tip that could help my investigation. For example, maybe in some revision over the past year, some anti-timing attack code was added to polarssl that uses excess cpu? Thanks."}}