Has there been any benchmarking done on thrift vs avro bindings in 0.7 codebase?
If one was about to bring into alpha production in the Jan 2011 timeframe, would going with avro be recommended? If one was to benchmark ... I'd be more interested in benchmarks that measure access to a node that actually has the data (i.e. ring awareness) and that are at CL:1 on the read. The CFs and their mutations have extremely low probability of concurrent writes (or overwrites) and are thus also configured for CL:1. I've got a pre-alpha (from my perspective) set of services that are using thrift from both PHP and Java (not hector). All developers are isolated behind scale agnostic tier ... so the changes to get onto 0.7/0.7.1 by end of year and shift to avro would be completely isolated from the remainder of the development team. Thanks in advance.
