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 <ADSM-L@VM.MARIST.EDU>
> 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
> ********************************************************
>

Reply via email to