Re: Experiences with Cassandra hardware planning

2010-10-25 Thread Jonathan Ellis
On Mon, Oct 25, 2010 at 3:10 PM, Eric Rosenberry wrote: >> I don't follow the reasoning there.  Row cache or fs cache, it will be >> hot after reading it once, the difference is that doing a read to the >> cached data is much faster from row cache. > > Yeah, I would have thought the same.  Benjami

Re: Experiences with Cassandra hardware planning

2010-10-25 Thread Eric Rosenberry
I am going to respond to multiple questions in one email to keep down the thread insanity: On Mon, Oct 25, 2010 at 12:39 AM, David Dabbs wrote: > Sorry, Eric I’m not following you. You’ve set the JVM’s processor > affinity so it only runs on one of the processors? > My understanding is that Li

Re: Experiences with Cassandra hardware planning

2010-10-25 Thread Jonathan Ellis
On Mon, Oct 25, 2010 at 10:25 AM, Edward Capriolo wrote: >> 2. We gave up on using Cassandra's row cache as loading any reasonable >> amount of data into the cache would take days/weeks with our tiny row size. >>  We instead are using file system cache. I don't follow the reasoning there. Row ca

Re: Experiences with Cassandra hardware planning

2010-10-25 Thread Edward Capriolo
On Mon, Oct 25, 2010 at 11:21 AM, Eric Rosenberry wrote: > Hey Chris- > That is tough to say as we started out with no data and have been > continuously loading data into the cluster.  Initially we had less data than > the amount of RAM in each node (48 gigs) but we have eventually exceeded > that

Re: Experiences with Cassandra hardware planning

2010-10-25 Thread Eric Rosenberry
Hey Chris- That is tough to say as we started out with no data and have been continuously loading data into the cluster. Initially we had less data than the amount of RAM in each node (48 gigs) but we have eventually exceeded that and now have many times more data on each node than in the entire

Re: Experiences with Cassandra hardware planning

2010-10-25 Thread Chris Burroughs
On 10/24/2010 11:16 PM, Eric Rosenberry wrote: > I wanted to share back to the community some of the learnings we have come > across including the hardware configuration we have been successful with > (YMMV). This is still a work in progress naturally. > > I have written up a detailed blog post a

RE: Experiences with Cassandra hardware planning

2010-10-25 Thread David Dabbs
org Subject: Re: Experiences with Cassandra hardware planning We have not started our JVM's with numactl. I am not sure what (if any) benefit there has been to turning on NUMA in the BIOS. Turning it on could have in fact reduced performance. I suspect that Java is only using memory from o

Re: Experiences with Cassandra hardware planning

2010-10-24 Thread Eric Rosenberry
We have not started our JVM's with numactl. I am not sure what (if any) benefit there has been to turning on NUMA in the BIOS. Turning it on could have in fact reduced performance. I suspect that Java is only using memory from one of the processors (since less than half of the physical memory is

RE: Experiences with Cassandra hardware planning

2010-10-24 Thread David Dabbs
Eric, Thanks for the detailed post! Did you need to start your JVMs with numactl in order to take advantage of NUMA? I know the board, OS and JVM must be configured properly, but it's not clear if the JVMs must be started with numactl. Thanks, David From: Eric Rosenberry [mailto:epros...@g