[
https://issues.apache.org/jira/browse/HADOOP-13597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15803116#comment-15803116
]
Xiao Chen commented on HADOOP-13597:
------------------------------------
Had a final pass of the patch, +1.
Verified the built documentation looks good.
Verified no perf regression on my local Max, in a simple non-ssl test, using
apache benchmark:
{{ab -n 10000 -c 10 -T "application/json" -p postfile
"http://IP:9600/kms/v1/keyversion/k1%408/_eek?eek_op=decrypt&user.name=whatever"}}
{noformat:title=before}
This is ApacheBench, Version 2.3 <$Revision: 1748469 $>
Copyright 1996 Adam Twiss, Zeus Technology Ltd, http://www.zeustech.net/
Licensed to The Apache Software Foundation, http://www.apache.org/
Benchmarking 172.16.3.181 (be patient)
Completed 1000 requests
Completed 2000 requests
Completed 3000 requests
Completed 4000 requests
Completed 5000 requests
Completed 6000 requests
Completed 7000 requests
Completed 8000 requests
Completed 9000 requests
Completed 10000 requests
Finished 10000 requests
Server Software: Apache-Coyote/1.1
Server Hostname: 172.16.3.181
Server Port: 9600
Document Path:
/kms/v1/keyversion/k1%408/_eek?eek_op=decrypt&user.name=whatever
Document Length: 84 bytes
Concurrency Level: 10
Time taken for tests: 1.881 seconds
Complete requests: 10000
Failed requests: 0
Total transferred: 3540000 bytes
Total body sent: 2940000
HTML transferred: 840000 bytes
Requests per second: 5316.11 [#/sec] (mean)
Time per request: 1.881 [ms] (mean)
Time per request: 0.188 [ms] (mean, across all concurrent requests)
Transfer rate: 1837.79 [Kbytes/sec] received
1526.30 kb/s sent
3364.10 kb/s total
Connection Times (ms)
min mean[+/-sd] median max
Connect: 0 0 0.3 0 17
Processing: 1 1 1.5 1 49
Waiting: 0 1 1.4 1 49
Total: 1 2 1.5 2 49
Percentage of the requests served within a certain time (ms)
50% 2
66% 2
75% 2
80% 2
90% 3
95% 3
98% 5
99% 7
100% 49 (longest request)
{noformat}
{noformat:title=after}
xiao-MBP:Downloads xiao$ ab -n 5000 -c 10 -T "application/json" -p postfile
"http://172.16.3.181:9600/kms/v1/keyversion/k1%408/_eek?eek_op=decrypt&user.name=whatever";
This is ApacheBench, Version 2.3 <$Revision: 1748469 $>
Copyright 1996 Adam Twiss, Zeus Technology Ltd, http://www.zeustech.net/
Licensed to The Apache Software Foundation, http://www.apache.org/
Benchmarking 172.16.3.181 (be patient)
Completed 500 requests
Completed 1000 requests
Completed 1500 requests
Completed 2000 requests
Completed 2500 requests
Completed 3000 requests
Completed 3500 requests
Completed 4000 requests
Completed 4500 requests
Completed 5000 requests
Finished 5000 requests
Server Software: Jetty(9.3.11.v20160721)
Server Hostname: 172.16.3.181
Server Port: 9600
Document Path:
/kms/v1/keyversion/k1%408/_eek?eek_op=decrypt&user.name=whatever
Document Length: 84 bytes
Concurrency Level: 10
Time taken for tests: 0.949 seconds
Complete requests: 5000
Failed requests: 0
Total transferred: 2315000 bytes
Total body sent: 1475000
HTML transferred: 420000 bytes
Requests per second: 5267.81 [#/sec] (mean)
Time per request: 1.898 [ms] (mean)
Time per request: 0.190 [ms] (mean, across all concurrent requests)
Transfer rate: 2381.83 [Kbytes/sec] received
1517.58 kb/s sent
3899.41 kb/s total
Connection Times (ms)
min mean[+/-sd] median max
Connect: 0 1 0.3 0 3
Processing: 1 1 0.8 1 12
Waiting: 0 1 0.7 1 11
Total: 1 2 0.9 2 12
ERROR: The median and mean for the initial connection time are more than twice
the standard
deviation apart. These results are NOT reliable.
Percentage of the requests served within a certain time (ms)
50% 2
66% 2
75% 2
80% 2
90% 3
95% 3
98% 4
99% 4
100% 12 (longest request)
{noformat}
(Tried 10000 but seems to hang around 6k for a while, guessing it's because of
some changed defaults etc. IMO as long as the latency is at the same level, we
can always tune the threads etc as needed.)
Committing this. Great work here [~jzhuge]! Do you mind file a follow-on to fix
the javac?
> Switch KMS from Tomcat to Jetty
> -------------------------------
>
> Key: HADOOP-13597
> URL: https://issues.apache.org/jira/browse/HADOOP-13597
> Project: Hadoop Common
> Issue Type: New Feature
> Components: kms
> Affects Versions: 2.6.0
> Reporter: John Zhuge
> Assignee: John Zhuge
> Attachments: HADOOP-13597.001.patch, HADOOP-13597.002.patch,
> HADOOP-13597.003.patch, HADOOP-13597.004.patch, HADOOP-13597.005.patch,
> HADOOP-13597.006.patch, HADOOP-13597.007.patch
>
>
> The Tomcat 6 we are using will reach EOL at the end of 2017. While there are
> other good options, I would propose switching to {{Jetty 9}} for the
> following reasons:
> * Easier migration. Both Tomcat and Jetty are based on {{Servlet
> Containers}}, so we don't have change client code that much. It would require
> more work to switch to {{JAX-RS}}.
> * Well established.
> * Good performance and scalability.
> Other alternatives:
> * Jersey + Grizzly
> * Tomcat 8
> Your opinions will be greatly appreciated.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
