Mailing-List: contact cassandra-commits-help@incubator.apache.org;
 run by ezmlm
Precedence: bulk
Reply-To: cassandra-dev@incubator.apache.org
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: Apache Wiki <wikidiffs@apache.org>
To: Apache Wiki <wikidiffs@apache.org>
Date: Thu, 19 Nov 2009 16:29:26 -0000
Message-ID: <20091119162926.19672.3075@eos.apache.org>
Subject: =?utf-8?q?=5BCassandra_Wiki=5D_Update_of_=22FAQ=22_by_JonathanEllis?=

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Cassandra Wiki" for=
 change notification.

The "FAQ" page has been changed by JonathanEllis.
http://wiki.apache.org/cassandra/FAQ?action=3Ddiff&rev1=3D27&rev2=3D28

--------------------------------------------------

  =3D=3D What kind of hardware should I run Cassandra on? =3D=3D
  =

  =3D=3D=3D Memory =3D=3D=3D
- The most recently written data resides in memory tables (aka [[MemtableTh=
resholds|memtables]]), but older data that has been flushed to disk can be =
kept in the OS's file-system cache. In other words, ''the more memory, the =
better'', (with 1GB being the absolute minimum).
+ The most recently written data resides in memory tables (aka [[MemtableTh=
resholds|memtables]]), but older data that has been flushed to disk can be =
kept in the OS's file-system cache. In other words, ''the more memory, the =
better'', with 1GB being the minimum recommended.
  =

  =3D=3D=3D CPU =3D=3D=3D
- FIXME
+ Many workloads will actually be CPU-bound in Cassandra before being memor=
y-bound.  Cassandra is highly concurrent and will make good use of however =
many cores you can give it.
+ =

  =

  =3D=3D=3D Disk =3D=3D=3D
  The short answer here is, ''at least 2 disks'', one to keep your `CommitL=
ogDirectory` on, the other to use in `DataFileDirectories`. The exact answe=
r though depends a lot on your usage so it's important to understand what i=
s going on here.