Hi Eric:
I'm running v8.1.8 with containers....here's what I have:
vm.dirty_background_ratio = 10
vm.dirty_ratio = 40
vm.dirty_expire_centisecs = 3000
vm.dirty_writeback_centisecs = 500
net.core.rmem_max = 212992
net.core.wmem_max = 212992
net.ipv4.tcp_rmem = 4096 87380 6291456
net.ipv4.tcp_wmem = 4096 16384 4194304
net.core.netdev_max_backlog = 1000
net.ipv4.tcp_moderate_rcvbuf = 1
net.ipv4.tcp_no_metrics_save = 0
[e1derley@yacht ~]$ free
total used free shared buff/cache
available
Mem: 528077736 17168096 1300116 394717640 509609524
114504416
Swap: 511996 48068 463928
[e1derley@yacht ~]$ lscpu
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
CPU(s): 48
On-line CPU(s) list: 0-47
Thread(s) per core: 2
Core(s) per socket: 12
Socket(s): 2
NUMA node(s): 2
Vendor ID: GenuineIntel
CPU family: 6
Model: 79
Model name: Intel(R) Xeon(R) CPU E5-2650 v4 @ 2.20GHz
Stepping: 1
CPU MHz: 2499.975
CPU max MHz: 2900.0000
CPU min MHz: 1200.0000
BogoMIPS: 4400.22
Virtualization: VT-x
L1d cache: 32K
L1i cache: 32K
L2 cache: 256K
L3 cache: 30720K
NUMA node0 CPU(s):
0,2,4,6,8,10,12,14,16,18,20,22,24,26,28,30,32,34,36,38,40,42,44,46
NUMA node1 CPU(s):
1,3,5,7,9,11,13,15,17,19,21,23,25,27,29,31,33,35,37,39,41,43,45,47
Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall
nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl
xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor
ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid dca sse4_1 sse4_2
x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm
abm 3dnowprefetch epb cat_l3 cdp_l3 intel_pt ibrs ibpb stibp tpr_shadow
vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms
invpcid rtm cqm rdt_a rdseed adx smap xsaveopt cqm_llc cqm_occup_llc
cqm_mbm_total cqm_mbm_local dtherm ida arat pln pts spec_ctrl intel_stibp
Lots of mem and db on ssds are most important.
Eric Wonderley
On Mon, Dec 9, 2019 at 8:38 AM Sasa Drnjevic <[email protected]> wrote:
> Hi Eric.
>
> Not using directory containers, but hope it would still help.
>
> Two servers (repl source and target) - each ISP v8.1 with 24 cores and
> 128 GB RAM. Backups stage to rnd disk volumes and then migrate to LTO7.
> All devices are on FC SAN.
>
> --------------------------------------------------
> 270 active nodes
> 4 TB / 1.5 mil files avg daily ingest
> --------------------------------------------------
> vm.dirty_background_ratio = 10
> vm.dirty_ratio = 40
> vm.dirty_expire_centisecs = 3000
> vm.dirty_writeback_centisecs = 500
> net.core.rmem_max = 212992
> net.core.wmem_max = 212992
> net.ipv4.tcp_rmem = 4096 87380 6291456
> net.ipv4.tcp_wmem = 4096 16384 4194304
> net.core.netdev_max_backlog = 1000
> net.ipv4.tcp_moderate_rcvbuf = 1
> net.ipv4.tcp_no_metrics_save = 0
> --------------------------------------------------
>
> I believe those are all RHEL7 defaults.
>
> Never had any performance issues.
>
> Rgds,
>
> --
> Sasa Drnjevic
> www.srce.unizg.hr/en/
>
>
>
>
>
> On 2019-12-09 8:48, Loon, Eric van (ITOP NS) - KLM wrote:
> > Hi guys,
> >
> > I received no response on my question down below. I know it's just a
> matter of cut-and-paste, so I really appreciate if you can have a look at
> my request.
> > Thank you very much in advance!
> >
> > Kind regards,
> > Eric van Loon
> > Air France/KLM Storage & Backup
> >
> > From: Loon, Eric van (ITOP NS) - KLM
> > Sent: donderdag 5 december 2019 14:22
> > To: ADSM-L <[email protected]>
> > Subject: Kernel parameters
> >
> > Hi guys,
> >
> > Our TSM 7.1 servers (with directory containers) were suffering from a
> very slow response for a long time. We already applied the kernel
> parameters specified in the installation guide and the SP Blueprints, but
> since we recently changed several other kernel parameters in one go, thing
> improved a lot. It's still not great, but at least it's not taking ages
> anymore to set up a new client session.
> > I'm interested in the value you are using on your Linux servers,
> especially for servers with a large workload on directory containers. If
> this is the case, can you please send me the output of the following
> commands:
> >
> > sysctl vm.dirty_background_ratio
> > sysctl vm.dirty_ratio
> > sysctl vm.dirty_expire_centisecs
> > sysctl vm.dirty_writeback_centisecs
> > sysctl net.core.rmem_max
> > sysctl net.core.wmem_max
> > sysctl net.ipv4.tcp_rmem
> > sysctl net.ipv4.tcp_wmem
> > sysctl net.core.netdev_max_backlog
> > sysctl net.ipv4.tcp_moderate_rcvbuf
> > sysctl net.ipv4.tcp_no_metrics_save
> >
> > Thank you VERY much for your help in advance!
> >
> > Kind regards,
> > Eric van Loon
> > Air France/KLM Storage & Backup
> > ********************************************************
> > For information, services and offers, please visit our web site:
> http://www.klm.com. This e-mail and any attachment may contain
> confidential and privileged material intended for the addressee only. If
> you are not the addressee, you are notified that no part of the e-mail or
> any attachment may be disclosed, copied or distributed, and that any other
> action related to this e-mail or attachment is strictly prohibited, and may
> be unlawful. If you have received this e-mail by error, please notify the
> sender immediately by return e-mail, and delete this message.
> >
> > Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or
> its employees shall not be liable for the incorrect or incomplete
> transmission of this e-mail or any attachments, nor responsible for any
> delay in receipt.
> > Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch
> Airlines) is registered in Amstelveen, The Netherlands, with registered
> number 33014286
> > ********************************************************
> >
>
