Performance Testing Tools

Steps to create an NFS Mount for pods Perform the below steps on NFS Server: In our case, the NFS is mounted on another different server. We have created a directory /MTCache and made the entry of the same in /etc/exports. The  /etc/exports  file on the NFS server contains the accessible NFS directories. The entry in /etc/exports on the NFS hosting server will be: /MTCache *(rw,sync,no_root_squash) NFS Options: Some options we can use in “/etc/exports” file for file sharing is as follows. 1.      ro: With the help of this option we can provide read only access to the shared files i.e client will only be able to read. 2.      rw: This option allows the client server to both read and write access within the shared directory. 3.      sync: Sync confirms requests to the shared directory only once the changes have been committed. 4.      no_subtree_check: This option prevents the subtree checking. When a shared directory is the subdirectory of a larger file system,

Today i want to share a command ss (Socket statistics) to investigate network and debug tcp connections. ss  is  used to dump socket statistics. It allows showing information similar to netstat.  It can display more TCP and state information than other tools. It is present in most of our Linux machines. ss commands has lot of options. To get all options: ss -help Few commands and outputs worth trying are as below: ss -t ->stands for tcp. Gives information about tcp connections that are available on the system #ss -t State       Recv-Q Send-Q                                Local Address:Port                                                 Peer Address:Port ESTAB       0      352                                   172.19.79.104:ssh                                                172.29.155.168:64045 ESTAB       0      0                                     172.19.79.104:54550                                               172.19.79.105:pcsync-https ESTAB   

Initial basic checks before proceeding to DB tunings in MSSQL: Check your SQL Server environment before tuning for performance Sometimes when we have issues with slow response for our DB queries, we think of tuning the query assuming the SQL Server is tuned and it may be problem with queries. But it is observed that it is better to make a common practice to check the basic configuration settings of the SQL server before we start to analyze the queries deeper. Today i will try to touch base some of those settings which we always need to check for proper settings of the SQL server Environment. Check 1: Database and Transaction log files on separate drives To obtain optimal SQL performance, it is recommended to separate the data and the log files onto separate physical drives. Placing both data AND log files on the same device can cause contention for that device, resulting in poor performance. Placing the files on separate drives allows the I/O activity to occur at the sa