You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@cassandra.apache.org by ae...@orange.com on 2016/03/09 10:54:37 UTC
[C*2.1]memtable_allocation_type: offheap_objects
Hi,
offheap_objects was removed in releases 3.2.x then reintroduced in release 3.4: I vould like to know if someone has used offheap_objects in Cassandra 2.1: stable or not, improvement observed or not...
Thanks.
Ahmed
_________________________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.
RE: [C*2.1]memtable_allocation_type: offheap_objects
Posted by ae...@orange.com.
Thank you !
Another question please : In the blog post (http://www.datastax.com/dev/blog/off-heap-memtables-in-Cassandra-2-1), it is noted that offheap_objects it effective for small values like ints or uuids as well. offheap_buffers for the tables with string or blobs.
in my case, the tables contains many columns with string type. But in cassandra.yaml, it is noted that offheap_objects is: native memory, heap buffer nio Eliminating overhead.
I must in all cases use offheap_objects?
Thanks.
De : Jeff Jirsa [mailto:jeff.jirsa@crowdstrike.com]
Envoyé : mercredi 9 mars 2016 17:13
À : user@cassandra.apache.org
Objet : Re: [C*2.1]memtable_allocation_type: offheap_objects
We use them. No signs of stability problems in 2.1 that we’ve attributed to offheap objects.
From: "aeljami.ext@orange.com<ma...@orange.com>"
Reply-To: "user@cassandra.apache.org<ma...@cassandra.apache.org>"
Date: Wednesday, March 9, 2016 at 1:54 AM
To: user
Subject: [C*2.1]memtable_allocation_type: offheap_objects
Hi,
offheap_objects was removed in releases 3.2.x then reintroduced in release 3.4: I vould like to know if someone has used offheap_objects in Cassandra 2.1: stable or not, improvementobservedor not…
Thanks.
Ahmed
_________________________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.
_________________________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.
Re: [C*2.1]memtable_allocation_type: offheap_objects
Posted by Jeff Jirsa <je...@crowdstrike.com>.
We use them. No signs of stability problems in 2.1 that we’ve attributed to offheap objects.
From: "aeljami.ext@orange.com"
Reply-To: "user@cassandra.apache.org"
Date: Wednesday, March 9, 2016 at 1:54 AM
To: user
Subject: [C*2.1]memtable_allocation_type: offheap_objects
Hi,
offheap_objects was removed in releases 3.2.x then reintroduced in release 3.4: I vould like to know if someone has used offheap_objects in Cassandra 2.1: stable or not, improvementobservedor not…
Thanks.
Ahmed
_________________________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.
Re: [C*2.1]memtable_allocation_type: offheap_objects
Posted by Jonathan Haddad <jo...@jonhaddad.com>.
Check out Al's Tuning Guide. He discusses offheap objects.
https://tobert.github.io/pages/als-cassandra-21-tuning-guide.html
On Wed, Mar 9, 2016 at 1:54 AM <ae...@orange.com> wrote:
> Hi,
>
>
>
> offheap_objects was removed in releases 3.2.x then reintroduced in
> release 3.4: I vould like to know if someone has used offheap_objects in
> Cassandra 2.1: stable or not, improvement observed or not…
>
>
>
> Thanks.
>
> Ahmed
>
>
>
> _________________________________________________________________________________________________________________________
>
> Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
> Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
>
> This message and its attachments may contain confidential or privileged information that may be protected by law;
> they should not be distributed, used or copied without authorisation.
> If you have received this email in error, please notify the sender and delete this message and its attachments.
> As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
> Thank you.
>
>