{"action":"closed","issue":{"url":"https://api.github.com/repos/shadowsocks/shadowsocks-libev/issues/2147","repository_url":"https://api.github.com/repos/shadowsocks/shadowsocks-libev","labels_url":"https://api.github.com/repos/shadowsocks/shadowsocks-libev/issues/2147/labels{/name}","comments_url":"https://api.github.com/repos/shadowsocks/shadowsocks-libev/issues/2147/comments","events_url":"https://api.github.com/repos/shadowsocks/shadowsocks-libev/issues/2147/events","html_url":"https://github.com/shadowsocks/shadowsocks-libev/issues/2147","id":350359629,"node_id":"MDU6SXNzdWUzNTAzNTk2Mjk=","number":2147,"title":"AES GCM really use of AES-NI extension on supported machine?","user":{"login":"xqdoo00o","id":12299238,"node_id":"MDQ6VXNlcjEyMjk5MjM4","avatar_url":"https://avatars1.githubusercontent.com/u/12299238?v=4","gravatar_id":"","url":"https://api.github.com/users/xqdoo00o","html_url":"https://github.com/xqdoo00o","followers_url":"https://api.github.com/users/xqdoo00o/followers","following_url":"https://api.github.com/users/xqdoo00o/following{/other_user}","gists_url":"https://api.github.com/users/xqdoo00o/gists{/gist_id}","starred_url":"https://api.github.com/users/xqdoo00o/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/xqdoo00o/subscriptions","organizations_url":"https://api.github.com/users/xqdoo00o/orgs","repos_url":"https://api.github.com/users/xqdoo00o/repos","events_url":"https://api.github.com/users/xqdoo00o/events{/privacy}","received_events_url":"https://api.github.com/users/xqdoo00o/received_events","type":"User","site_admin":false},"labels":[{"id":483234800,"node_id":"MDU6TGFiZWw0ODMyMzQ4MDA=","url":"https://api.github.com/repos/shadowsocks/shadowsocks-libev/labels/third-party%20bug","name":"third-party bug","color":"5319e7","default":false}],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":10,"created_at":"2018-08-14T09:58:46Z","updated_at":"2018-09-12T06:02:49Z","closed_at":"2018-09-12T06:02:49Z","author_association":"NONE","body":"### What version of shadowsocks-libev are you using?\r\nlastest build 3.2.0\r\n\r\n### What operating system are you using?\r\ndebian 9 x86_64\r\n\r\n### What did you do?\r\nrun iperf test.\r\n\r\n### What did you expect to see?\r\niperf performance good\r\n\r\n### What did you see instead?\r\nOn the same machine, when I use chacha20-ietf-poly1305, the iperf result is similar between ss-libev and go-ss2(install from lastest source).\r\nBut when I use aes-(256 or 128)-gcm, go-ss2 iperf result is **3~4 times** difference with ss-libev iperf result.\r\n\r\n```\r\nAES-128-GCM\r\nss-libev      go-ss2\r\n130Mbps       600Mbps\r\n\r\nAES-256-GCM\r\nss-libev      go-ss2\r\n125Mbps       550Mbps\r\n```\r\n\r\nso I wonder if AES GCM really use AES-NI extension?\r\n\r\n### What is your config in detail (with all sensitive info masked)?\r\nlibsodium 1.0.16 mbedTLS 2.12\r\n**iperf-libev.sh**\r\n\r\n#!/bin/bash\r\nnumber=40960000\r\nmethod='aes-256-gcm'\r\n\r\nss-tunnel -k test -m $method -l 8387 -L 127.0.0.1:8388 -s 127.0.0.1 -p 8389 &\r\nss_tunnel_pid=$!\r\nss-server -k test -m $method -s 127.0.0.1 -p 8389 &\r\nss_server_pid=$!\r\n\r\niperf -s -p 8388 &\r\niperf_pid=$!\r\n\r\nsleep 1\r\n\r\niperf -c 127.0.0.1 -p 8387 -n $number\r\n\r\nsleep 2\r\n\r\nkill $ss_tunnel_pid\r\nkill $ss_server_pid\r\nkill $iperf_pid\r\n\r\nsleep 1\r\necho \"Test Finished\"\r\n\r\n**iperf-go.sh**\r\n\r\n#!/bin/bash\r\nnumber=40960000\r\nmethod='AEAD_AES_256_GCM'\r\n\r\nshadowsocks2 -c 'ss://'${method}':@:8389' -tcptun :8387=localhost:8388 &\r\nss_tunnel_pid=$!\r\nshadowsocks2 -s 'ss://'${method}':@:8389' &\r\nss_server_pid=$!\r\n\r\niperf -s -p 8388 &\r\niperf_pid=$!\r\n\r\nsleep 1\r\n\r\niperf -c 127.0.0.1 -p 8387 -n $number\r\n\r\nsleep 2\r\n\r\nkill $ss_tunnel_pid\r\nkill $ss_server_pid\r\nkill $iperf_pid\r\n\r\nsleep 1\r\necho \"Test Finished\"\r\n"}}
{"actor":{"display_login":"xqdoo00o"}}