The TCP settings are basically "how much RAM to use to buffer data for TCP
sessions, per session", which translates roughly to maximum TCP window
size. You can actually calculate approximately what you need by just
multiplying bandwidth and latency (10,000,000,000bps * .0001s * 1GB/8Gb =
125KB buf
19 at 4:54 PM
To: "user@cassandra.apache.org"
Subject: Re: Cassandra Recommended System Settings
Message from External Sender
Thanks Elliott!
How do you know if there is too much RAM used for those settings?
Which metrics do you keep track of?
What would you recommend instead?
Best,
Thanks Elliott!
How do you know if there is too much RAM used for those settings?
Which metrics do you keep track of?
What would you recommend instead?
Best,
Sergio
On Mon, Oct 21, 2019, 1:41 PM Elliott Sims wrote:
> Based on my experiences, if you have a new enough kernel I'd strongly
> su
Based on my experiences, if you have a new enough kernel I'd strongly
suggest switching the TCP scheduler algorithm to BBR. I've found the rest
tend to be extremely sensitive to even small amounts of packet loss among
cluster members where BBR holds up well.
High ulimits for basically everything
Hello!
This is the kernel that I am using
Linux 4.16.13-1.el7.elrepo.x86_64 #1 SMP Wed May 30 14:31:51 EDT 2018
x86_64 x86_64 x86_64 GNU/Linux
Best,
Sergio
Il giorno lun 21 ott 2019 alle ore 07:30 Reid Pinchback <
rpinchb...@tripadvisor.com> ha scritto:
> I don't know which distro and version
I don't know which distro and version you are using, but watch out for
surprises in what vm.swappiness=0 means. In older kernels it means "only use
swap when desperate". I believe that newer kernels changed to have 1 mean
that, and 0 means to always use the oomkiller. Neither situation is str
Hello everyone!
Do you have any setting that you would change or tweak from the below list?
sudo cat /proc/4379/limits
Limit Soft Limit Hard Limit Units
Max cpu time unlimitedunlimitedseconds
Max file size un
