I was under the impression that it is multiple requests using a single connectin PARALLEL not serial as they have request ids and the responses do as well so you can send a request while a previous request has no response just yet.
I think you do get a big speed advantage from the asynchronous nature as you do not need to hold up so many threads in your webserver while you have outstanding requests being processed. The thrift async was not exactly async like I am suspecting the new java driver is, but have not verified(I hope it is)
From: Aaron Turner <firstname.lastname@example.org<mailto:email@example.com>>
Reply-To: "firstname.lastname@example.org<mailto:email@example.com>" <firstname.lastname@example.org<mailto:email@example.com>>
Date: Sunday, May 5, 2013 5:27 PM
To: cassandra users <firstname.lastname@example.org<mailto:email@example.com>>
Subject: Re: hector or astyanax
On Sun, May 5, 2013 at 1:09 PM, Derek Williams <firstname.lastname@example.org<mailto:email@example.com>> wrote:
The binary protocol is able to multiplex multiple requests using a single connection, which can lead to much better performance (similar to HTTP vs SPDY). This is without comparing the performance of thrift vs binary protocol, which I assume the binary protocol would be faster since it is specialized for cassandra requests.
Curious why you think multiplexing multiple requests over a single connection (serial) is faster then multiple requests over multiple connections (parallel)?
And isn't Thrift a binary protocol?
http://synfin.net/ Twitter: @synfinatic
http://tcpreplay.synfin.net/ - Pcap editing and replay tools for Unix & Windows
Those who would give up essential Liberty, to purchase a little temporary
Safety, deserve neither Liberty nor Safety.
-- Benjamin Franklin
"carpe diem quam minimum credula postero"