1. Erasure Code Configuration The default erasure parity configuration is as follows: Erasure Set Size Default Parity (EC:M) 1 EC:0 2-3 EC:1 4-5 EC:2 6 - 7 EC:3 8 - 16 EC:4 The maximum parity is ERASURE_SET_SIZE/2, meaning the number of parity blocks cannot exceed the number of data blocks.

1. Background While testing the performance of NFS Over RDMA, I found that reading a 4M file could actually reach 45GB/s. 1 2 3 fio -numjobs=128 -fallocate=none -iodepth=2 -ioengine=libaio -direct=1 -rw=read -bs=4M --group_reporting -size=100m -time_based -runtime=30 -name=fio-test -directory=/data1/nfs READ: bw=42.3GiB/s (45.4GB/s), 42.3GiB/s-42.3GiB/s (45.4GB/s-45.4GB/s), io=1269GiB (1363GB), run=30019-30019msec Yet the disk’s 4M multi-threaded read performance is only 6 GB/s.

1. About FLOPs FLOPs (Floating Point Operations Per Second) refers to the number of floating-point operations performed per second. Specifically: A single floating-point addition, such as a + b, counts as one floating-point operation. A single floating-point multiplication, such as a * b, also counts as one floating-point operation. Other basic floating-point operations, such as division and square root, can also be counted as one floating-point operation.

1. Installation Ubuntu 1 apt-get install -y iperf3 CentOS 1 yum install -y iperf3 2. Parameters The principle behind iperf3 is that the client sends packets to the server so the network can be analyzed. It has two running modes: client and server. The iperf3 parameters fall into three groups: common parameters, client parameters, and server parameters.

This article mainly offers optimization advice on Django fields and queries, and also introduces a performance analysis tool called Django-silk. I hope it helps you develop high-performance Django projects. 1. DBA’s Advice 1.1 Table Field Design Avoid null values; null values are hard to optimize queries around and take up extra index space Prefer INT over BIGINT, and describe fields as accurately as possible Use enums or integers instead of string types Use TIMESTAMP instead of DATETIME Do not put more than 20 fields in a single table Store IPs as integers 1.