Yes. But I haven't yet seen a workload with enough data that that would matter, that wasn't more cpu bound than disk space bound, so that would usually be premature optimization.
On Tue, May 25, 2010 at 2:23 PM, Robert Edmonds <edmo...@debian.org> wrote: > On 2010-05-25, Jonathan Ellis <jbel...@gmail.com> wrote: >> That's true. But fundamentally Cassandra is expected to use more >> space than mysql for a few reasons; usually the biggest factor is that >> Cassandra has to write out each column name in each row, since column >> names are dynamic unlike in mysql where you declare the columns once >> for the whole table. > > does this mean that using short column names (e.g., "f" instead of > "first_seen") will save space when storing billions of rows? > > -- > Robert Edmonds > edmo...@debian.org > > -- Jonathan Ellis Project Chair, Apache Cassandra co-founder of Riptano, the source for professional Cassandra support http://riptano.com
