+
+**High Performance**
+
+openGauss breaks through the bottleneck of multi-core CPU, 2-way Kunpeng 128 core 1.5 million TPMC on disk-based row store and 3.5 million TPMC on MOT (Memory-Optimized Tables) Engine.
+
+**Partitions**
+
+Divide key data structure shared by internal threads into different partitions to reduce lock access conflicts. For example, CLOG uses partition optimization to solve the bottleneck of ClogControlLock.
+
+**NUMA Structure**
+
+Malloc key data structures help reduce cross CPU access. The global PGPROC array is divided into several parts according to the number of NUMA nodes, solving the bottleneck of ProcArrayLock.
+
+**Binding Cores**
+
+Bind NIC interrupts to different cores and bind cores to different background threads to avoid performance instability due to thread migration between cores.
+
+**ARM Optimization**
+
+Optimize atomic operations based on ARM platform LSE instructions, implementing efficient operation of critical sections.
+
+**SQL Bypass**
+
+Optimize SQL execution process through SQL bypass, reducing CPU execution overhead.
+
+**High Reliability**
+
+Under normal service loads, the RTO is less than 10 seconds, reducing the service interruption time caused by node failure.
+
+**Parallel Recovery**
+
+When the Xlog is transferred to the standby node, the standby node flushs the Xlog to storage medium. At the meantime, the Xlog is sent to the redo recovery dispatch thread. The dispatch thread sends the Xlog to multiple parallel recovery threads to replay. Ensure that the redo speed of the standby node keeps up with the generation speed of the primary host. The standby node is ready in real time, which can be promoted to primary instantly.
+
+**MOT Engine (beta release)**
+
+The Memory-Optimized Tables (MOT) storage engine is a transactional rowstore optimized for many-core and large memory and delivering extreme OLTP performance and high resources utilization. With data and indexes stored totally in-memory, a NUMA-aware design, algorithms that eliminate lock and latch contention and query native compilation (JIT), MOT provides low latency data access and more efficient transaction execution. See MOT Engine documentation (https://opengauss.org/en/docs/1.0.0/docs/Developerguide/mot.html).
+
+**Security**
+
+openGauss supports account management, account authentication, account locking, password complexity check, privilege management and verification, transmission encryption, and operation audit, protecting service data security.
+
+**Easy Operation and Maintenance**
+
+openGauss integrates AI algorithms into databases, reducing the burden of database maintenance.
+
+- **SQL Prediction**
+
+openGauss supports SQL execution time prediction based on collected historical performance data.
+
+- **SQL Diagnoser**
+
+openGauss supports the diagnoser for SQL execution statements, finding out slow queries in advance..
+
+- **Automatical Parameter Adjustment**
+
+openGauss supports automatically adjusting database parameters, reducing the cost and time of parameter adjustment.
+
+## Installation
+
+### Creating a Configuration File
+
+Before installing the openGauss, you need to create the clusterconfig.xml file. The configuration file in the XML format contains the information about the server where the openGauss is deployed, installation path, IP address, and port number. This file is used to guide how to deploy the openGauss. You need to configure the configuration file according to the actual deployment requirements.
+
+The following describes how to create an XML configuration file based on the deployment solution of one primary node and one standby node.
+The information of value is only an example. You can replace it as required. Each line of information is commented out.
+
+```
+
+
-**High Performance**
+**高性能**
+
+openGauss突破了多核CPU的瓶颈，实现两路鲲鹏128核150万tpmC，内存优化表（MOT）引擎达350万tpmC。
+
+**数据分区**
-openGauss breaks through the bottleneck of multi-core CPU, 2-way Kunpeng 128 core 1.5 million TPMC on disk-based row store and 3.5 million TPMC on MOT (Memory-Optimized Tables) Engine.
+内部线程共享的关键数据结构进行数据分区，减少加锁访问冲突。比如CLOG就采用分区优化，解决ClogControlLock锁瓶颈。
-**Partitions**
+**NUMA化内核数据结构**
-Divide key data structure shared by internal threads into different partitions to reduce lock access conflicts. For example, CLOG uses partition optimization to solve the bottleneck of ClogControlLock.
+关键数据结构NUMA化分配，减少跨CPU访问。比如全局PGPROC数组按照NUMA Node的数目分为多份，分别在对应NUMA Node上申请内存。解决ProcArrayLock锁瓶颈。
-**NUMA Structure**
+**绑核优化**
-Malloc key data structures help reduce cross CPU access. The global PGPROC array is divided into several parts according to the number of NUMA nodes, solving the bottleneck of ProcArrayLock.
+把网络中断绑核和后台业务线程绑核区分开，避免运行线程在核间迁移造成的性能不稳定。
-**Binding Cores**
+**ARM指令优化**
-Bind NIC interrupts to different cores and bind cores to different background threads to avoid performance instability due to thread migration between cores.
+结合ARM平台的原子操作lse进行优化，实现关键互斥变量原子高效操作。
-**ARM Optimization**
+**SQL BY PASS**
-Optimize atomic operations based on ARM platform LSE instructions, implementing efficient operation of critical sections.
+通过SQL BY PASS优化SQL执行流程，简化CPU执行开销。
-**SQL Bypass**
+**高可靠**
-Optimize SQL execution process through SQL bypass, reducing CPU execution overhead.
+正常业务负载情况下，RTO小于10秒，降低节点故障导致的业务不可用时间。
-**High Reliability**
+**并行恢复**
-Under normal service loads, the RTO is less than 10 seconds, reducing the service interruption time caused by node failure.
+主机日志传输到备机时，备机日志落盘的同时，发送给重做恢复分发线程，分发线程根据日志类型和日志操作的数据页发给多个并行恢复线程进行日志重做，保证备机的重做速度跟上主机日志的产生速度。这样备机实时处于ready状态，从而实现瞬间故障切换。
-**Parallel Recovery**
-When the Xlog is transferred to the standby node, the standby node flushes the Xlog to storage medium. At the meantime, the Xlog is sent to the redo recovery dispatch thread. The dispatch thread sends the Xlog to multiple parallel recovery threads to replay. Ensure that the redo speed of the standby node keeps up with the generation speed of the primary host. The standby node is ready in real time, which can be promoted to primary instantly.
+**MOT引擎（Beta发布）**
-**MOT Engine (beta release)**
+内存优化表（MOT）存储引擎是一个专为多核大内存优化的存储引擎，具有极高的联机事务处理（OLTP）性能和资源利用率。MOT的数据和索引完全存储在内存中，通过NUMA感知执行，算法消除闩锁争用以及查询JIT本地编译，提供低时延数据访问及高效事务执行。更多请参考MOT引擎文档（https://opengauss.org/zh/docs/1.0.0/docs/Developerguide/%E5%86%85%E5%AD%98%E8%A1%A8%E7%89%B9%E6%80%A7.html）。
-The Memory-Optimized Tables (MOT) storage engine is a transactional rowstore optimized for many-core and large memory and delivering extreme OLTP performance and high resources utilization. With data and indexes stored totally in-memory, a NUMA-aware design, algorithms that eliminate lock and latch contention and query native compilation (JIT), MOT provides low latency data access and more efficient transaction execution. See MOT Engine documentation (https://opengauss.org/en/docs/1.0.0/docs/Developerguide/mot.html).
+**安全**
-**Security**
+openGauss支持账号管理，账号认证，口令复杂度检查，账号锁定，权限管理和校验，传输加密，操作
+审计等全方位的数据库安全能力，保护业务满足安全要求。
-openGauss supports account management, account authentication, account locking, password complexity check, privilege management and verification, transmission encryption, and operation audit, protecting service data security.
+**易运维**
-**Easy Operation and Maintenance**
+openGauss将AI算法集成到数据库中，减少数据库维护的负担。
-openGauss integrates AI algorithms into databases, reducing the burden of database maintenance.
+- **SQL预测**
-- **SQL Prediction**
+openGauss根据收集的历史性能数据进行编码和基于深度学习的训练及预测，支持SQL执行时间预测。
-openGauss supports SQL execution time prediction based on collected historical performance data.
+- **SQL诊断器**
-- **SQL Diagnoser**
+openGauss支持SQL执行语句的诊断器，提前发现慢查询。
-openGauss supports the diagnoser for SQL execution statements, finding out slow queries in advance..
+- **参数自动调整**
-- **Automatic Parameter Adjustment**
+openGauss通过机器学习方法自动调整数据库参数，提高调参效率，降低正确调参成本。
-openGauss supports automatically adjusting database parameters, reducing the cost and time of parameter adjustment.
-## Installation
+## 安装
-### Creating a Configuration File
+### 创建配置文件
-Before installing the openGauss, you need to create a configuration file. The configuration file in the XML format contains the information about the server where the openGauss is deployed, installation path, IP address, and port number. This file is used to guide how to deploy the openGauss. You need to configure the configuration file according to the actual deployment requirements.
+在安装openGauss之前，需要创建clusterconfig.xml配置文件。XML文件包含部署openGauss的服务器信息、安装路径、IP地址以及端口号等。用于告知openGauss如何部署。用户需根据不同场配置对应的XML文件。
-The following describes how to create an XML configuration file based on the deployment solution of one primary node and one standby node.
-The information of value is only an example. You can replace it as required. Each line of information is commented out.
+下面以一主一备的部署方案为例，说明如何创建XML配置文件。
+以下value取值信息仅为示例，可自行替换。每行信息均有注释进行说明。
```
-
+
6&
z(BuT!TVm4G`6Fh)vR(COL)>vV$)=rzFx(9Bo%X4o_{XVA#|b*S%dJR=%lH_SZ+PXk
zB(bdnVfZPYGN0MfEyR~xrZPV!4CVD&jo<`lZTzI+mz}Xihr<~q%kUZXhiaLOEynyw
zkGH8$=6)iq_-PVqe9$Gx^q>eEBQ