Super - thank you for help :)
On Thu, Nov 3, 2011 at 6:55 PM, Jonathan Ellis jbel...@gmail.com wrote:
Relying on that was always a terrible idea because you could easily
OOM before it could help. There's no substitute for don't make the
caches too large in the first place.
We're working on
According to source code, JNA is being used to call malloc and free. In
this case each cached row will be serialized into RAM.
We must be really careful when defining cache size - to large size would
cause out of memory. Previous Cassandra releases has logic that would
decrease cache size if heap
Relying on that was always a terrible idea because you could easily
OOM before it could help. There's no substitute for don't make the
caches too large in the first place.
We're working on https://issues.apache.org/jira/browse/CASSANDRA-3143
to make cache sizing easier.
On Thu, Nov 3, 2011 at
Up, also interested in answers to questions below.
Best regards/ Pagarbiai
Viktor Jevdokimov
Senior Developer
Email: viktor.jevdoki...@adform.com
Phone: +370 5 212 3063
Fax: +370 5 261 0453
J. Jasinskio 16C,
LT-01112 Vilnius,
Lithuania
Disclaimer: The information contained in this message
I've just found, that JNA will be not used from 1.1 release -
https://issues.apache.org/jira/browse/CASSANDRA-3271
I would be also nice to know what was the reason for this decision.
Regards,
Maciej
On Wed, Nov 2, 2011 at 1:34 PM, Viktor Jevdokimov
viktor.jevdoki...@adform.com wrote:
Up, also
