There will be a small performance improvement from not having the app->cluster latency. If ran on same system (which I wouldn’t recommend) the latency would be pretty irrelevant anyway unless you are fighting for sub millisecond latency (in which case get off the JVM). You would be able to access the storage proxy and such directly which could provide other performance wins and customizations. Also any disk IO, cpu heavy work or object creation could throw off Cassandra’s performance. Cassandra can peg out CPU, disk io, and the JVMs GC itself since it is designed to fully utilize a system.
I think its an Ok idea for unit/integration tests or dev environments. I would say however that the massive maintence complexity of keeping your embedded version up to date alone (bug fixes and awesome new feature X!) would make embedding worth it only for edge scenarios. I would recommend against it. --- Chris Lohfink On Apr 16, 2014, at 10:13 AM, Sávio Teles <savio.te...@lupa.inf.ufg.br> wrote: > Is it advisable to run the embedded Cassandra in production? > > > 2014-04-16 12:08 GMT-03:00 Sávio Teles <savio.te...@lupa.inf.ufg.br>: > I'm running a cluster with Cassandra and my app embedded. > > Regarding performance, it is better to run embedded Cassandra? > > What are the implications of running an embedded Cassandra ? > > Tks > -- > Atenciosamente, > Sávio S. Teles de Oliveira > voice: +55 62 9136 6996 > http://br.linkedin.com/in/savioteles > Mestrando em Ciências da Computação - UFG > Arquiteto de Software > Laboratory for Ubiquitous and Pervasive Applications (LUPA) - UFG > > > > -- > Atenciosamente, > Sávio S. Teles de Oliveira > voice: +55 62 9136 6996 > http://br.linkedin.com/in/savioteles > Mestrando em Ciências da Computação - UFG > Arquiteto de Software > Laboratory for Ubiquitous and Pervasive Applications (LUPA) - UFG
