title: How to choose more efficient SSL in Java
body: <p>Our application is for load testing arbitrary HTTP(s) servers. We use java with Netty to make lots of concurrent requests. When using the Netty java SSL client and SSLEngine, we are now seeing CPU at 100% for relatively low levels of concurrency. I suspect that the client and server are negotiating the most secure choice available, and I want to do what is likely the opposite (choose the option that will cause the smallest CPU load on our system). We must use SSL, but there is no concern about security. How do we go about configuring the SSLEngine to use a better algorithm?</p>
  
  <p>I realize that the server (which is out of our control) limits the choices. But, we need to use a less CPU intensive option if available. We are running this on Amazon's EC2 with c3.large instances.</p>