• Please help support our sponsors by considering their products and services.
    Our sponsors enable us to serve you with this high-speed Internet connection and fast webservers you are currently using at ADSM.ORG.
    They support this free flow of information and knowledge exchange service at no cost to you.

    Please welcome our latest sponsor Tectrade . We can show our appreciation by learning more about Tectrade Solutions
  • Community Tip: Please Give Thanks to Those Sharing Their Knowledge.

    If you receive helpful answer on this forum, please show thanks to the poster by clicking "LIKE" link for the answer that you found helpful.

  • Community Tip: Forum Rules (PLEASE CLICK HERE TO READ BEFORE POSTING)

    Click the link above to access ADSM.ORG Acceptable Use Policy and forum rules which should be observed when using this website. Violators may be banned from this website. This notice will disappear after you have made at least 3 posts.

Requesting kernel parameters

#1
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
 
#3
Very slow response on several commands like Q STGPOOL which took at least 45 seconds. Each new client or admin session also took very long to initiate, sometimes up to a minute.
We had a case open at IBM which went all up to development, but they had no clue. The only thing they saw was that the delay was in the DB2 identification part, but nor TSM support nor DB support was able to fix it.
Only after we changed all these parameters in one go, the performance improved a lot. That's why I would like to compare them with other users.
Kind regards,
Eric
 

moon-buddy

ADSM.ORG Moderator
#4
When you said you followed the Blueprint, I am assuming you had all bases covered.

But...

What Intel platform are you running TSM on?
# of CPU?
Local or SAN disk for the DB2 volumes and LOGS?
FC speed?
Memory size?

I am running TSM on Linux on Cisco blades and never needed to apply the tuning parameters you listed. A typical TSM server for me has:

48 CPU cores
64 or 128 GB of RAM as the case maybe
internal disk of RAID 1, 300 GB capacity for OS/TSM binaries
DB Volume/LOGS on Netapp via FC, 8 Gbps
 
#5
With all due respect, I don't want to go into details here. Like stated earlier, the performance issue seems to be fixed after changing several kernel parameters in one go.
I'm just curious about the values others have set.
 

moon-buddy

ADSM.ORG Moderator
#6
With all due respect, I don't want to go into details here. Like stated earlier, the performance issue seems to be fixed after changing several kernel parameters in one go.
I'm just curious about the values others have set.
Like I said, I don't have to do all that tweaking.
 

Advertise at ADSM.ORG

If you are reading this, so are your potential customer. Advertise at ADSM.ORG right now.

UpCloud high performance VPS at $5/month

Get started with $25 in credits on Cloud Servers. You must use link below to receive the credit. Use the promo to get upto 5 month of FREE Linux VPS.

The Spectrum Protect TLA (Three-Letter Acronym): ISP or something else?

  • Every product needs a TLA, Let's call it ISP (IBM Spectrum Protect).

    Votes: 18 19.6%
  • Keep using TSM for Spectrum Protect.

    Votes: 57 62.0%
  • Let's be formal and just say Spectrum Protect

    Votes: 10 10.9%
  • Other (please comement)

    Votes: 7 7.6%

Forum statistics

Threads
31,541
Messages
134,441
Members
21,613
Latest member
spineale
Top