Part of the decision is the backend. Cassandra vs HBase. I've setup both and in my opinion Cassandra is easier to setup and manage. With Cassandra you can start with a 3 node cluster and then expand as your usage increases. I've read articles where they recommend that HBase needs to start with 6 to 10 before you can increase for expansion.
I'm in the middle of converting the Kairos code over to use CQL (was using thrift) and I'm testing performance. I have 4 identical computers (i5 4 core, 16gig ram, ssd's), one is a kairos node and the other 3 are Cassandra nodes with a replication factor of 1. With the CQL code I can push 1 million metrics/sec through Kairos. Granted this test doesn't account for protocol parsing - the metrics are generated within the Kairos service.
The changeover to CQL will make kairos queries faster, I'll have real numbers in the next few weeks. I have tried to see how many queries/sec I can run through the same setup, each query only hitting a dozen data points - this matches a use case I'm looking at for work. Querying a few data points I can run about 500 queries/sec through the single kairos node. Your mileage will vary depending on the number of data points you hit in the query.
You will get a smaller data footprint with opentsdb as they have a background compaction process that goes back over your inserted data and compacts the columns (both a good and bad thing).
Does that help?
Brian