Re:Finding Kafka’s throughput limit in Dropbox infrastructure
by pmalynin on Friday February 01, 2019 @01:18PM
(#19056782)
I'm not exactly sure what that has to do with the throughput of TLS, especially considering that it's 99% likely that its implemented in a native library (openssl, etc).
[ Parent
| on HN ]
Re:Finding Kafka’s throughput limit in Dropbox infrastructure
by deanmoriarty on Friday February 01, 2019 @01:22PM
(#19056835)
Java TLS implementation is 99.9% implemented in Java itself (look at JSSE), openssl was ditched a long, long time ago.
Not that I would necessarily expect the throughput to be significantly different than the native version considering the good performance of JITted Java, but was just commenting on your assumption.
Re:Finding Kafka’s throughput limit in Dropbox infrastructure
by pmalynin on Friday February 01, 2019 @01:26PM
(#19056882)
Oh, I didn't know that, thanks for the clarification.
I mostly work with C++, Python and Node in my day to day, so my assumptions are biased.
Re:Finding Kafka’s throughput limit in Dropbox infrastructure
by 75dvtwin on Friday February 01, 2019 @11:55PM
(#19061177)
Take a look at conscrypt
https://github.com/google/conscrypt
According to reports into Jetty folks, using conscript for TLS, gives 10x improvements
https://webtide.com/conscrypting-native-ssl-for-jetty/
Note, that, from what I read, conscrypt is not compiled for any of the BSDs so if you are testing there, you will have to compile conscrypt yourself
Re:Finding Kafka’s throughput limit in Dropbox infrastructure
by halbritt on Friday February 01, 2019 @01:21PM
(#19056822)
The problem is that it's not implemented in the native library. That's why the throughput is so abysmal.
Re:Finding Kafka’s throughput limit in Dropbox infrastructure
by anotherhue on Friday February 01, 2019 @02:08PM
(#19057375)
It also prevents use of the sendfile optimisation -- meaning a lot of Kafka perf disappears.