No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.


FusionCube DB 3.1 Database Best Practice 03 (Oracle RAC 11g R2)

Rate and give feedback :
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
(Optional) Configuring NUMA Nodes for VBS Processes

(Optional) Configuring NUMA Nodes for VBS Processes

  • If a CH242 V3 or CH242 V5 serves as a database node and multiple IB NICs are used, refer to this section to optimize the node performance.
  • Perform the following operations on each database node.

If a CH242 V3 or CH242 V5 serves as a database node and two IB NICs are configured, bind NUMA nodes to FusionStorage processes after CPU groups are configured.

During the process initialization, each FusionStorage process applies for a memory pool required by all its services, and all I/O access reuses the buffer in the memory pool. The memory in a memory pool on a specific NUMA node is not migrated to other NUMA nodes as the FusionStorage threads change.

There are also NUMA nodes for devices like IB NICs. You can run a command to view the NUMA node that a device belongs to. You can modify the FusionStorage startup script to determine which NUMA node is started and ensure that the started NUMA node is the node to which an IB NIC belongs. This reduces the delay in copying data from the device cache to the FusionStorage process memory pool and improves performance on 4-socket servers.

Log in to each database node as user root, and edit the VBS process startup script to bind the VBS process to its NUMA node.


  1. Run the following commands:

    [root@dbn01~ ]# cp /opt/dsware/agent/script/ /opt/dsware/agent/script/dsware_vbs.sh_bak
    [root@dbn01~ ]# vi /opt/dsware/agent/script/

    Run the :36 command to move the cursor to line 36 and press o to start a new line and enter the insert mode.

    Figure 2-7 Run :36 to move the cursor to line 36.

  2. Add the following content in bold to the file from line 37:

        let nodeid=$vbs_uid%2 
        if [ $nodeid = 0 ];then     
        elif [ $nodeid = 1 ];then     
        numactl --cpunodebind=$nodeid --membind=$nodeid $vbs_name -u $1 -c $2 >/dev/null 2>&1     

    Figure 2-8 shows the data after modification.

    Figure 2-8 Data after modification

  3. Save the changes, run the following commands to restart the VBS processes, and check whether the processes are successfully started.

    [root@dbn01~ ]# killall -9 dsware_vbs 
    [root@dbn01~ ]# ps -ef | grep dsware_vbs 

  4. Run the following commands to check whether the NUMA nodes are successfully bound to the VBS processes:

    [root@dbn01 ~]# top -H -n 5 b >/tmp/log
    [root@dbn01 ~]# cat /tmp/log | grep data-net|awk '{print $1}'|sort -n|uniq|xargs numastat -p

    If the information shown in the preceding figure is displayed, the binding is successful.

Updated: 2018-12-26

Document ID: EDOC1100035759

Views: 20592

Downloads: 30

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Previous Next