Message from discussion
Project Voldemort vs Cassandra for write heavy apps
Received: by 10.14.1.150 with SMTP id 22mr1292232eed.22.1296586954038;
Tue, 01 Feb 2011 11:02:34 -0800 (PST)
X-BeenThere: project-voldemort@googlegroups.com
Received: by 10.14.26.28 with SMTP id b28ls517981eea.5.p; Tue, 01 Feb 2011
11:02:32 -0800 (PST)
Received: by 10.14.1.150 with SMTP id 22mr1291772eed.22.1296586864378;
Tue, 01 Feb 2011 11:01:04 -0800 (PST)
Received: by 10.14.1.150 with SMTP id 22mr1291771eed.22.1296586864330;
Tue, 01 Feb 2011 11:01:04 -0800 (PST)
Return-Path: <tsalora...@gmail.com>
Received: from mail-ey0-f170.google.com (mail-ey0-f170.google.com [209.85.215.170])
by gmr-mx.google.com with ESMTPS id t6si6944957eeh.0.2011.02.01.11.01.03
(version=TLSv1/SSLv3 cipher=RC4-MD5);
Tue, 01 Feb 2011 11:01:03 -0800 (PST)
Received-SPF: pass (google.com: domain of tsalora...@gmail.com designates 209.85.215.170 as permitted sender) client-ip=209.85.215.170;
Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of tsalora...@gmail.com designates 209.85.215.170 as permitted sender) smtp.mail=tsalora...@gmail.com; dkim=pass (test mode) header...@gmail.com
Received: by mail-ey0-f170.google.com with SMTP id 5so4601592eyf.15
for <project-voldemort@googlegroups.com>; Tue, 01 Feb 2011 11:01:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=gmail.com; s=gamma;
h=domainkey-signature:mime-version:in-reply-to:references:date
:message-id:subject:from:to:content-type:content-transfer-encoding;
bh=FMna0PWKvTzc9d9E2I9P2xBdsWDtXiVYyDcosIes9FI=;
b=sKxkkx4Y1ImMZk0qFHJbi5uLxleS7vnqZCo9PbrZSE/awxTgZYD7MjJhRszN/Rpv+k
3KrhDNtgoX8OzgKdsTtVS33Jha6xa2m7BPJMDVZPI0Nn7/YhREUXiwRTnzTTp7UUNX44
uh7aAIRYADU845psFKMtw18z0qOLiPwohgRAY=
DomainKey-Signature: a=rsa-sha1; c=nofws;
d=gmail.com; s=gamma;
h=mime-version:in-reply-to:references:date:message-id:subject:from:to
:content-type:content-transfer-encoding;
b=jvXxijadkhSz3mlsX9LtHMdoerLuPrOy53PJjMfylsKXzAzlfysbd99hCIkBk6L/Hl
n8Gu/pf7XQIFhYdgdnko4SxHEHacd7Wjm79vd4Ig2kyDPYLNYwQLF+Wi64K38s6eWjOG
a2rj1aLzbwFK5mSgkTGRpCu0dENY2r+WGLKkM=
MIME-Version: 1.0
Received: by 10.14.10.208 with SMTP id 56mr1425284eev.31.1296586863084; Tue,
01 Feb 2011 11:01:03 -0800 (PST)
Received: by 10.14.119.72 with HTTP; Tue, 1 Feb 2011 11:01:00 -0800 (PST)
In-Reply-To: <AANLkTimvwq7A3NrdMT=OqfJFHOda8=r+xvOgtVauj...@mail.gmail.com>
References: <718ee4d0-a9b6-4f66-9ba1-cdf34224f...@m27g2000prj.googlegroups.com>
<AANLkTi=emNe2Q0UeQpPgN=2SEK_SdsbG6ePRn2C41...@mail.gmail.com>
<66b21552-7572-4ba2-b1c5-1fc9b77ab...@k30g2000yqb.googlegroups.com>
<AANLkTimvwq7A3NrdMT=OqfJFHOda8=r+xvOgtVauj...@mail.gmail.com>
Date: Tue, 1 Feb 2011 11:01:00 -0800
Message-ID: <AANLkTim_2v1cENPYg+K8dT4Ev=jYFFicwXJ3zmxm8...@mail.gmail.com>
Subject: Re: [project-voldemort] Re: Project Voldemort vs Cassandra for write
heavy apps
From: Tatu Saloranta <tsalora...@gmail.com>
To: project-voldemort@googlegroups.com
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
On Tue, Feb 1, 2011 at 8:49 AM, John Cohen <john.java.w...@gmail.com> wrote=
:
> Hi All,
>
> Benchmark is just one part of the overall system consideration that
> you have to evaluate based on your business goal. =A0Another one is how
> easy or difficult something can be done with a particular persistent
> implementation layer. =A0For example backups/restore (point in time
> recovery), "toolings" that you may need to debug, or inspect your
> system, usability, etc.
>
> Consider not just benchmark in your evaluation,
Fully agreed -- there is sometimes tendency to overestimate value of
performance. And even with performance there are multiple trade-offs
between basic latency (~=3Dmaximum speed) and throughput (~=3Dscalability
with concurrency).
Beyond backups/restores, ability to seamlessly add/remove nodes is
often important, and something not many distributed systems handle
ideally (how to bootstrap, do config files need to be manually
modified etc).
With respect to Voldemort, there seem to be developments to create
high(er)performance mysql/innodb-based backends, which could give
significant gains to performance and possibly allow better backup
functionality as well (since RDBMSs typically have well-developed
functionality in this area). Ability to plug different backends is
nice if and when backends do have different trade-offs.
-+ Tatu +-