Well, you can make Cassandra work on a single box (or multiple instances on a
single box if need be). My experimental/dev cluster that my team plays with to
try things out is 6 nodes running on 6 rather small cloud VM's and it works
fine. So I'd say yes, it work in the merely big scale.
On Feb
Afternoon all - I'm playing with 0.7beta3 on some boxes I have here at the
office and while checking out the stats from one of my tests I'm seeing Write
Latency being reported as "0.009 ms". I haven't done any timing yet in my
client, but is this really microsecond latency, or is there a mismatc
Alvin - assuming I understand what you're after correctly, why not make a CF
Name_Address(name, address). Modifying the Cassandra methods to do the "join"
you describe seems like overkill to me...
-Paul
On Sep 15, 2010, at 7:34 PM, Alvin UW wrote:
Hello,
I am going to build an index to join t
This isn't directly related to Cassandra, but we did a bunch of I/O and disk
load testing about 2 years ago when we started migrating to a new MTA platform
looking specifically at filesystem performance. We compared EXT2, EXT3, GFS2,
XFS and EXT4 under RHEL5/CentOS5 on a commodity box using 6 in
