, caching, pooling, etc) of Cassandra 1.X.
Right now i come to know that following client exists:
1) Hector(Java)
2) Thrift (Java)
3) Kundera (Java)
With Regards,
Amit
--
Thomas Spengler
Chief Technology Officer
--
Thomas Spengler
Chief Technology Officer
TopTarif Internet GmbH, Pappelallee 78-79, D-10437 Berlin
Tel.: (030) 2000912 0 | Fax: (030) 2000912 100
thomas.speng...@toptarif.de | www.toptarif.de
Amtsgericht Charlottenburg, HRB
graphs since the
upgrade, but they show promising results compared to the slope of the same
graph before the upgrade to 1.1.2
So my advice is give 1.1.2 a shot - just be mindful of
https://issues.apache.org/jira/browse/CASSANDRA-4411
On 2012-07-26, at 2:18 AM, Thomas Spengler wrote:
I
to 1.1.2
So my advice is give 1.1.2 a shot - just be mindful of
https://issues.apache.org/jira/browse/CASSANDRA-4411
On 2012-07-26, at 2:18 AM, Thomas Spengler wrote:
I saw this.
All works fine upto version 1.1.0
the 0.8.x takes 5GB of memory of an 8GB machine
the 1.0.x takes between
25, 2012 at 1:21 AM, Thomas Spengler
thomas.speng...@toptarif.de wrote:
No one has any idea?
we tryed
update to 1.1.2
DiskAccessMode standard, indexAccessMode standard
row_cache_size_in_mb: 0
key_cache_size_in_mb: 0
Our next try will to change
SerializingCacheProvider
Is there any way to limit the off heap memory usage for cassandra 1.1.X
Thx
--
Thomas Spengler
is standard
The memory usage grows upto the whole memory is used.
Just for information, as we had cassandra 1.0.3, we used
* DiskAccessMode is standard, indexAccessMode is mmap
* and the ram-usage was ~4GB
can anyone help?
With Regards
--
Thomas Spengler
