> I wonder why disk_access_mode property is not in cassandra.yaml (looking
into trunk right now)
I think there's a prehistoric reason why it was removed but I can't
remember right now.
> Do you all think we can add it there with brief explanation what each
option does?
We could reinclude it as l
Thanks for starting this discussion, Paulo!
Shall we also share this thread with @user?
On Wed, 6 Sep 2023 at 16:35, C. Scott Andreas wrote:
> Supportive of switching the default to mmap_index_only as well.
>
> I don’t have numbers handy to share, but my experience has been
> significantly lowe
I wonder why disk_access_mode property is not in cassandra.yaml (looking into
trunk right now). Do you all think we can add it there with brief explanation
what each option does?
From: Caleb Rackliffe
Sent: Wednesday, September 6, 2023 21:08
To: dev@cass
+100 to this
We'd have to come up w/ a pretty compelling counterexample to NOT switch
the default to mmap_index_only at this point.
On Wed, Sep 6, 2023 at 11:40 AM Brandon Williams wrote:
> Given https://issues.apache.org/jira/browse/CASSANDRA-17237 I think it
> makes sense. At the least I thi
Given https://issues.apache.org/jira/browse/CASSANDRA-17237 I think it
makes sense. At the least I think we should restore disk_access_mode
so that users are more aware of the options available.
Kind Regards,
Brandon
On Wed, Sep 6, 2023 at 10:50 AM Paulo Motta wrote:
>
> Hi,
>
> I've been bitte
Supportive of switching the default to mmap_index_only as well.
I don’t have numbers handy to share, but my experience has been significantly
lower read latency and I wouldn’t run with auto. I’ve also not observed
substantial heap pressure after switching - it was strictly an improvement.
- Sco
Hi,
I've been bitten by OOMs with disk_access_mode:auto/mmap that were fixed by
changing to disk_access_mode:mmap_index_only. In a particular benchmark I
got 5x more read throughput on 3.11.x with disk_access_mode:
mmap_index_only vs disk_access_mode: auto/mmap.
Changing disk_access_mode to mmap_
I think most of the time people actually use netty _with_ native. This might
have been introduced when we were tried to make shaded in-JVM dtest jars. If
all tests are passing, and we actually do have a confirmtion that native Netty
is being used, I would say +1 to remove `noNative`.
Just to m
