...
If your application using bsr is write-intensive and has frequent writes of small size, it is recommended to increase the activity log size. Otherwise, metadata updates will occur frequently and write performance may suffer. The default is 6001.following is an example of expanding the AL size to 65001.
| Code Block |
|---|
>bsradm create-md --al-stripe-size-kB 288 r0
...
>bsradm dump-md r0
...
al-stripe-size-4k 72;
... |
Specify al-extents and congestion-extents.
| Code Block |
|---|
resource <resource> {
disk {
al-extents 65001;
...
}
net {
congestion-extents 58501; # 90% of the al-extents
}
} |
| Code Block |
|---|
resource <resource> {
disk {
al-extents 6001;
...
}
...
} |
sndbuf-size
The transmission buffer implements the optimization of the transmission amount through buffering. Since TCP/IP transmission is an ACK-based protocol, the more the segment is transmitted, the greater the protocol overhead. Therefore, from a network transmission perspective, it is advantageous to collect and send as much data as possible when sending data. Since the transmit buffer implements this part, optimization can be achieved naturally. In particular, in a situation in which a small amount of data is continuously transmitted, the amount of data can be greatly improved by collecting and sending the data to the transmission buffer queue for a certain amount. You should consider optimizing with sndbuf-size in the following situations:
...