[
https://issues.apache.org/jira/browse/TS-2753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14008271#comment-14008271
]
Wei Sun commented on TS-2753:
-----------------------------
Thanks [~briang]'s reply. I tweaked the spdy parts after Alan M. Carroll's
change to avoid conflict.
[~bcall], I was trying to use 'proxy.process.ssl.total_handshake_time' to
measure the E2E SSL handshake time from server perspective (2 RTT for full
handshake, 1 RTT for abbreviated handshake). Test result of the initial patch
is as below. Whereas calculating the endtime after SSL_accept immediately
showed one constant RTT.
ping 10.87.xx.xxx
64 bytes from 10.87.xx.xxx: icmp_seq=0 ttl=56 time=346.152 ms
64 bytes from 10.87.xx.xxx: icmp_seq=1 ttl=56 time=440.084 ms
64 bytes from 10.87.xx.xxx: icmp_seq=2 ttl=56 time=342.770 ms
64 bytes from 10.87.xx.xxx: icmp_seq=3 ttl=56 time=343.027 ms
64 bytes from 10.87.xx.xxx: icmp_seq=4 ttl=56 time=344.504 ms
Full handshake: echo | openssl s_client -connect 10.87.xx.xxx:443 -sess_out
/tmp/ssl 2>/dev/null
Abbreviated handshake: echo | openssl s_client -connect 10.87.xx.xxx:443
-sess_in /tmp/ssl 2>/dev/null
-bash-4.1$ sudo tail -f traffic.out | grep "ssl handshake time"
[May 25 02:59:28.224] Server {0x2b67a6524700} DEBUG: (ssl) ssl handshake
time:689301499
[May 25 02:59:31.824] Server {0x2b67a6625700} DEBUG: (ssl) ssl handshake
time:344400710
> Add more SPDY and HTTPS statistics
> -----------------------------------
>
> Key: TS-2753
> URL: https://issues.apache.org/jira/browse/TS-2753
> Project: Traffic Server
> Issue Type: Improvement
> Components: SPDY
> Reporter: Wei Sun
> Assignee: Bryan Call
> Labels: spdy, yahoo
> Fix For: 5.0.0
>
> Attachments: TS-2753_1.diff
>
>
> Adding stats to spdy helps monitoring and troubleshooting, it would be good
> to define and add spdy specific stats.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
