Table of Contents |
---|
...
- Check the performance of BAB through BAB usage and latency.
You can check the usage rate of the BAB set by calculation of "2.4. Physical Memory Specifications".
- You can see where bottlenecks have occurred by increasing or decreasing the latency value.
Output Sample
- Capacity : Indicates the BAB size set in the resource, in Kilobytes.
- Use (Size) : Indicates BAB usage rate and Size. The unit of size is Kilobytes.
- BAB Latency is the current (cur), average (avg), maximum (max), and minimum (min) values for the TX, RX, Compress, and Decompress items. The unit is microseconds.
Code Block theme DJango title memusage collapse true < general output > [root@c73-p1 dgkim]# drx-ctl mem all -------------------------------------------------------------------------------------- Name Capacity Use (Size) Full Counts -------------------------------------------------------------------------------------- DR-1-3-c73-p2-c73-p1 716800 [>>>>>>>.....................] 23% (163277) 0 10240 [............................] 0% (0) - -------------------------------------------------------------------------------------- DR-2-3-c73-p2-c73-p1 512000 [............................] 0% (0) 0 10240 [............................] 0% (0) - -------------------------------------------------------------------------------------- Active bab counts : 2 < verbose output > [root@c73-p1 dgkim]# drx-ctl mem all -v ---------------------------------------------------------------------------------------------------------- Name Capacity Begin End Use (Size) Full Counts ---------------------------------------------------------------------------------------------------------- DR-1-3-c73-p2-c73-p1 716800 340236152 504137496 [>>>>>>>.....................] 22% (160060) 0 10240 0 0 [............................] 0% (0) - ---------------------------------------------------------------------------------------------------------- DR-2-3-c73-p2-c73-p1 512000 64273922 64273922 [............................] 0% (0) 0 10240 0 0 [............................] 0% (0) - ---------------------------------------------------------------------------------------------------------- Active bab counts : 2 ---------------------------------------------------------------------------------------------------------- name Latency cur avg max min ---------------------------------------------------------------------------------------------------------- DR-1-3-c73-p2-c73-p1 TX BAB 00:00:00.000000 00:00:00.443516 00:00:06.765142 00:00:00.000101 RX BAB 00:00:00.000000 00:00:00.000000 00:00:00.000000 00:00:00.000000 Compress 00:00:00.000088 00:00:00.000087 00:00:00.001439 00:00:00.000001 Decompress 00:00:00.000000 00:00:00.000000 00:00:00.000000 00:00:00.000000 ---------------------------------------------------------------------------------------------------------- DR-2-3-c73-p2-c73-p1 TX BAB 00:00:00.000000 00:00:00.001627 00:00:00.004173 00:00:00.000261 RX BAB 00:00:00.000000 00:00:00.000000 00:00:00.000000 00:00:00.000000 Compress 00:00:00.000000 00:00:00.000113 00:00:00.001440 00:00:00.000001 Decompress 00:00:00.000000 00:00:00.000000 00:00:00.000000 00:00:00.000000 ---------------------------------------------------------------------------------------------------------- Active bab counts : 2 [root@c73-p1 dgkim]#
...
Type | System | Level range | Remarks |
---|---|---|---|
ZLIB | SW | 1~9 | - |
LZ4 | SW | 1~9 | - |
NONE | - | - | OFF |
The command to set the compression plug-in is as follows.
Type | Commands | Example output | |||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
ZLIB | drx-ctl set compress zlib [level] [connect name] |
| |||||||||
LZ4 | drx-ctl set compress lz4 [level] [connect name] |
| |||||||||
NONE | drx-ctl set compress none 0 [connect name] |
|
7.3.3 Number of compressing threads
...
- Commands
Code Block theme DJango title process-thread-count collapse true < Configuration > [root@c73-qat-1 drbd.d]# drx-ctl set process-thread-count 10 Result: done. [root@c73-qat-1 drbd.d]# < Check > [root@c73-qat-1 drbd.d]# drx-ctl show all ... ip-verification=on process-thread-count=10 [root@c73-qat-1 drbd.d]#
7.4. Others
For DRX Appliance, you can perform optimizations on the local replication I/O reception intervals that work with DRBD. DRX is primarily designed to perform buffering in the application address space, so performance may vary depending on the receiving performance of the OS kernel of the appliance, which is directly linked to DRBD. Therefore, you can tune the receive buffer of this OS kernel socket to further enhance RX receive performance. To ensure that the OS kernel has enough receive buffers, it is necessary to apply the following to the OS kernel.
...
- Change TCP socket buffer size
- Server used for testing : Server of /wiki/spaces/PX/pages/901775481
- References link : https://www.ibm.com/support/knowledgecenter/en/SSZTET_10.1/smpi01/smpi01_tysfbpjp.html
- Default : 208KBytes
Code Block theme DJango [root@c73-qat-1 drbd.d]# sysctl -a | grep net.core.[rw]mem net.core.rmem_default = 212992 net.core.rmem_max = 212992 net.core.wmem_default = 212992 net.core.wmem_max = 212992 [root@c73-qat-1 drbd.d]#
- Modify command : Change the max entry to 2 MBytes.
Code Block theme DJango sysctl -w net.core.rmem_max="2097152" sysctl -w net.core.wmem_max="2097152"
Info The set value is not an absolute value and the performance result may be different depending on server and network environment.