Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: pass (athena.apache.org: domain of jbellis@gmail.com designates
 74.125.82.43 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :content-type:content-transfer-encoding;
        b=F6IOFJno+4tj1eLOCAd4Fp2SaioSw0o08b8kggcseNZnzr5+CurHNrydF8nIr5U+7x
         9ga6GOa+4/YJQZvlUVhalNiQuvlzoDhk4AMKZ9YMSrA2dCO6ExM0oOuUsNJFwo2AFpS3
         gQGXfLPOlNjLMvyPbV3EqdFBKmlpcBhje00sU=
MIME-Version: 1.0
In-Reply-To: <AANLkTimYdI0lZ_OaEMXKbBEAZNvWXmx46G9Or_sgY3sO@mail.gmail.com>
References: <AANLkTinPzfdoCtt_yvBBFD6oM-GAG_nrQcyLvcV4ftGu@mail.gmail.com>
	<AANLkTil-aJGKRzEOTtshbb3Pd4MUVBk1D4SDuPOEiF_P@mail.gmail.com>
	<AANLkTimCBEHyBs5AjI4WuCvCGYrBR64f-Sc_tcU9xDzu@mail.gmail.com>
	<AANLkTilZ6Rd6tD_6fCu1vVkZeXMb842zqEXX9SIkJhBn@mail.gmail.com>
	<AANLkTimYdI0lZ_OaEMXKbBEAZNvWXmx46G9Or_sgY3sO@mail.gmail.com>
From: Jonathan Ellis <jbellis@gmail.com>
Date: Tue, 25 May 2010 13:27:15 -0500
Message-ID: <AANLkTikm3t4C1MJBeDVtnZ7otC57h7YnoLtC7trm9vTP@mail.gmail.com>
Subject: Re: Why Cassandra is "space inefficient" compared to MySQL?
To: user@cassandra.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

the only place we use a java serializer is for the BitSet in bloom filters.

On Tue, May 25, 2010 at 12:37 PM, Chris Goffinet <goffinet@digg.com> wrote:
> My money is on the fact that the serializer is just horribly verbose. It'=
s
> using a basic set of the java serializer.
> -Chris
>
>
> On Tue, May 25, 2010 at 10:02 AM, Ryan King <ryan@twitter.com> wrote:
>>
>> Also, timestamps for each column.
>>
>> -ryan
>>
>> On Tue, May 25, 2010 at 5:41 AM, Jonathan Ellis <jbellis@gmail.com> wrot=
e:
>> > That's true. =A0But 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.
>> >
>> > 2010/5/25 Peter Sch=FCller <scode@spotify.com>:
>> >>> Could you please tell me why?
>> >>
>> >> There might be pending sstable removals on disk, which won't happen
>> >> until GC or restart. If you just did a bulk insert and checked
>> >> diskspace immediately afterwards, I think this is a possible
>> >> explanation.
>> >>
>> >> (See "Write path" on
>> >> http://wiki.apache.org/cassandra/ArchitectureInternals)
>> >>
>> >> --
>> >> / Peter Schuller aka scode
>> >>
>> >
>> >
>> >
>> > --
>> > Jonathan Ellis
>> > Project Chair, Apache Cassandra
>> > co-founder of Riptano, the source for professional Cassandra support
>> > http://riptano.com
>> >
>
>


--=20
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder of Riptano, the source for professional Cassandra support
http://riptano.com