TLS support in fbench about vespa HOT 8 CLOSED

How much work is this I wonder. Are there some other hhtp benchmark suites out there that are able to do that ? Or is it fairly simple.

from vespa.

We could wrap the connect/read/write/shutdown logic in fbench with OpenSSL SSL_* calls, or alternatively create a new TLS socket implementation in FastOS (fbench uses FastOS sockets today) to make it more generally available. Either way we'd need some kind of key/certificate store and ability to pass keys/certs to the application.

For other tools, it seems both wrk and httperf support TLS, but I have no prior experience with either of them.

from vespa.

Another alternative is to create a new benchmark tool written in Java. There are multiple performant HTTP client implementations in Java. A Java implementation have numerous advantages, e.g integration with Athenz and programmatic APIs.

from vespa.

That is definitely true. My mind was aimed at groundwork for future "all RPC over TLS" functionality, but no inherent reason for why that has to be connected to this task.

from vespa.

wrk is blazingly fast compared to "ab" and I think it's faster than httperf. When doing quick comparisons on my local machine it would outperform anything else I used and is now my default http performance testing tool.

from vespa.

Hi, how can I contribute to this project? I know very little java. Where should I start?

from vespa.

By learning Java (or C++) I guess?

from vespa.

Implemented in #7288

from vespa.